maze.co
Observed Aug 11, 2026, 03:14 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.
maze.co is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting maze.co under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.
Watch maze.co Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Google Workspace
Amazon
Google Search ConsoleDomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.
Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.
This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.
DNS Records
A 4
3.162.103.1283.162.103.543.162.103.403.162.103.71
MX 5
1aspmx.l.google.com10alt3.aspmx.l.google.com10alt4.aspmx.l.google.com5alt1.aspmx.l.google.com5alt2.aspmx.l.google.com
TXT 8
_cf-custom-hostname.compliance=f55475fa-fbeb-4477-8b56-4ca06955779bgoogle-site-verification=-dJOQBWiYUsfnnk3eO5FtpLmhBe7-NgxQ7ClL9HUhHAgoogle-site-verification=28b8M5Sj0_rkgBrDOkmUyvcv7T4-QjzNMtO0-KDcsZwgoogle-site-verification=2cogUAqw02nvlYgRm1iNYAkWwoVTBjcQrW7-v5x0n2Mgoogle-site-verification=D5aaUEGGpTzGT2A4En9PqJ2gdC8K0YdqucXbpgXyBgIgoogle-site-verification=eFXujLjlSNGFTxQ4jYphg-bIXX4W3N3gZweJ093TvT4google-site-verification=i52Splgzk4sdbUG-rcfDn2UxrbJMusBmkq9_X-zbWpov=spf1 redirect=maze.co.hosted.spf-report.com
NS 4
ns-1436.awsdns-51.orgns-2001.awsdns-58.co.ukns-311.awsdns-38.comns-807.awsdns-36.net
SOA 1
ns-2001.awsdns-58.co.uk awsdns-hostmaster.amazon.com
CAA 7
issue "amazon.com"issue "amazonaws.com"issue "letsencrypt.org"issue "pki.goog"issuewild "amazon.com"issuewild "amazonaws.com"issuewild "letsencrypt.org"
MCP_RECORDS 1
v=spf1 -all
DMARC_RECORDS 1
v=DMARC1;p=reject;fo=1;rua=mailto:b18abbe7@mxtoolbox.dmarc-report.com;ruf=mailto:b18abbe7@forensics.dmarc-report.com;pct=100
BIMI_RECORDS 1
v=spf1 -all
MTA_STS_RECORDS 1
v=spf1 -all
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
maze.co |
C=US, O=Amazon, CN=Amazon RSA 2048 M01 | Sat, 02 Jan 2027 23:59:59 +0000 |
Amazon RSA 2048 M01 |
C=US, O=Amazon, CN=Amazon Root CA 1 | Fri, 23 Aug 2030 22:21:28 +0000 |
Amazon Root CA 1 |
C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Services Root Certificate Authority - G2 | Thu, 31 Dec 2037 01:00:00 +0000 |
Subdomains (1)
Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; the only network request the check makes is for the published public keys.
Verify this receiptEd25519 Receipt
- Receipt ID
rcpt_5d57a670b9199a3a- Output Hash
72325a324352f22d525d054e8808b94812decb850f1040c818bdf1cef04b23fc- Signature
ed25519:d658726012da97fc65c7b3ff39a063071312c9498f517307dcf61b60e71942a684ad28fe8bf2e5ee05ec810e14913ca1023170efe26045d4449861552af24905- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast