I did set up a Google Cloud Storage Bucket with index.html and test.html and what I see, when I go to my domain:
See: doc.s3.amazonaws.com/2006-03-01 in:
<?xml version='1.0' encoding='UTF-8'?>
<ListBucketResult xmlns='http://doc.s3.amazonaws.com/2006-03-01'>
<Name>my-domain.com</Name>
<Prefix></Prefix>
<Marker></Marker>
<IsTruncated>false</IsTruncated>
<Contents><Key>index.html</Key>
<Generation>1555969892676799</Generation>
<MetaGeneration>1</MetaGeneration>
<LastModified>2019-04-22T21:51...</LastModified>
<ETag>"...."</ETag>
<Size>25</Size></Contents><Contents>
<Key>test.html</Key>
etc..
I do not have amazon account.
Despite that string being present in the namespace, the response to that request is not coming from AWS.
Google Cloud Storage (GCS) has two APIs. One is JSON-based and looks like most of Google's APIs (called the JSON API), and the other is XML-based and is designed to be interoperable with some cloud storage tools and libraries that work with S3. The idea is that, if you already use such a tool, such as the Python boto library, using GCS can be accomplished by changing the URL and credentials. Clients parsing XML responses likely validate XML namespaces, and so they expect to see something like the string "http://doc.s3.amazonaws.com/2006-03-01" as part of the protocol.
You're sending a request to the XML API (either via storage.googleapis.com, BUCKET_NAME.storage.googleapis.com, or via a CNAME DNS redirect to Cloud Storage) , and so the resulting message tries to provide an interoperable response.