uzer.me
Observed Aug 2, 2026, 16:12 UTC (6h 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 3
172.234.27.71172.239.193.161172.234.27.37
MX 1
20mx156.hostedmxserver.com
TXT 1
v=spf1 -all
NS 2
ns2.parklogic.comns1.parklogic.com
SOA 1
ns1.parklogic.com hostmaster.uzer.me
MCP_RECORDS 1
v=spf1 -all
DMARC_RECORDS 1
v=spf1 -all
BIMI_RECORDS 1
v=spf1 -all
MTA_STS_RECORDS 1
v=spf1 -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_8543b8ff7e9e3a07- Output Hash
2ac83d84bf7797ba0cc6d9a928243eef7237d1c2b3309c508bd9beb79ed28916- Signature
ed25519:6ed725d53369254e2a3c152d05d31b404aeb5182f088823d06007039a990decbc48094c0ca87d2d2bac8e47a85214cc4d82ff9963d2efc44224994f9beb13304- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast