anchor-world.com
Observed Aug 2, 2026, 18:33 UTC (8d ago). Every field below was attested with an Ed25519 signature at scan time.
anchor-world.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting anchor-world.com 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 anchor-world.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.DomainDrift 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 2
125.22.54.146119.226.7.148
MX 1
0bombaybizemail.anchor-world.com
TXT 2
_m8q5b83fjhd76tv1alkizx5ti7qor5vv=spf1 a mx ptr +ip4:103.21.58.247 ~all
NS 2
jaime.ns.cloudflare.comkiki.ns.cloudflare.com
SOA 1
jaime.ns.cloudflare.com dns.cloudflare.com
MCP_RECORDS 1
v=spf1 a mx ip4:209.126.161.0/24 ip4:66.240.213.0/24 ip4:71.6.134.0/24 ip4:209.126.183.0/24 ip4:209.126.148.0/24 ip4:71.6.220.0/24 ip4:216.98.139.0/24 ip4:66.240.205.0/24 ip4:209.126.156.0/24 ip4:216.75.9.0/24 ip4:71.6.177.0/24 ip4:216.75.37.0/24 ip4:216.75.21.0/24 ip4:216.75.58.0/24 ~all
DMARC_RECORDS 1
v=DMARC1; p=none; rua=mailto:admin@fastdnshost.com;
BIMI_RECORDS 1
v=spf1 a mx ip4:209.126.161.0/24 ip4:66.240.213.0/24 ip4:71.6.134.0/24 ip4:209.126.183.0/24 ip4:209.126.148.0/24 ip4:71.6.220.0/24 ip4:216.98.139.0/24 ip4:66.240.205.0/24 ip4:209.126.156.0/24 ip4:216.75.9.0/24 ip4:71.6.177.0/24 ip4:216.75.37.0/24 ip4:216.75.21.0/24 ip4:216.75.58.0/24 ~all
MTA_STS_RECORDS 1
v=spf1 a mx ip4:209.126.161.0/24 ip4:66.240.213.0/24 ip4:71.6.134.0/24 ip4:209.126.183.0/24 ip4:209.126.148.0/24 ip4:71.6.220.0/24 ip4:216.98.139.0/24 ip4:66.240.205.0/24 ip4:209.126.156.0/24 ip4:216.75.9.0/24 ip4:71.6.177.0/24 ip4:216.75.37.0/24 ip4:216.75.21.0/24 ip4:216.75.58.0/24 ~all
TLS Certificates (0)
None.
Subdomains (0)
None observed.
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_b77d83122abc26ed- Output Hash
2392c4cbd67fcf3180d23525d6a7dcb668f8b0ac68fa53746cffcae8e0eba3ad- Signature
ed25519:91a052d7e99a20f1832b1b471ebf139fcd1556d02000895a48bc17932660b57f12208afe0eb7a3c5a96b0b544e60c5d4fa278ed87a3976c30cada7ea5fee1906- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast