yfdpco4.com
Observed Aug 2, 2026, 08:53 UTC (9h 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.196.46
MX 1
300\~
TXT 1
~
NS 2
ns2.nsresolution.comns1.nsresolution.com
SOA 1
ns1.nsresolution.com abuse.confluence-networks.com
MCP_RECORDS 1
~
DMARC_RECORDS 1
~
BIMI_RECORDS 1
~
MTA_STS_RECORDS 1
~
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_a6dd1798ac4ff7f0- Output Hash
6872814b102ece129a01742a7b2b9cbd10252138afefd5e3537a6b7d4cd3a69e- Signature
ed25519:6a8cfda442297b0155de84954c108156b5a5420589b45e5f14bd708a6901dcf0be093bdeb6accd2b8ee5cd5e95aef27b753bab22c3535f119f7f304e6c2b310c- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast