zsank.com
Observed Aug 2, 2026, 13:30 UTC (14h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.
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 1
208.91.197.46
MX 1
300\~
TXT 1
v=spf1 a -all
NS 2
sk.s5.ans1.ns148.ztomy.comsk.s5.ans2.ns148.ztomy.com
SOA 1
sk.s5.ans1.ns148.ztomy.com abuse.confluence-networks.com
MCP_RECORDS 1
v=spf1 a -all
DMARC_RECORDS 1
v=spf1 a -all
BIMI_RECORDS 1
v=spf1 a -all
MTA_STS_RECORDS 1
v=spf1 a -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; nothing leaves your machine.
Verify this receiptEd25519 Receipt
- Receipt ID
rcpt_ad9b8b9d235489ad- Output Hash
66a5dca9ba936afedb2d47e49ed80b99dc1d846f34ca99f1760492da64d86a97- Signature
ed25519:472b49f4b308761650feefcff218dc10c48003930d0407d6ccc2f7fca9063c06488ed3f02d8be885b93ae7db3c474832942dadff3a6e88ba36f31148d0d24f0f- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast