vemo.com
Observed Aug 3, 2026, 00:18 UTC (54m 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.239.193.161172.234.27.37172.234.27.71
MX 1
70mx156.hostedmxserver.com
TXT 1
v=spf1 -all
NS 2
ns2.parklogic.comns1.parklogic.com
SOA 1
ns1.parklogic.com hostmaster.vemo.com
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_e71cd2ff9ca2fb55- Output Hash
42c61e75a40507ffbde090698706618c7772c1cb191d8fcc67d51f8d3a460ac0- Signature
ed25519:470e3ac5e6b5915be3ea479286a814cb46e364c0c356db9c5e41843f64ad17c4920f01f336d696ed36477edeb98f01a9678caca68bf7de9364a9699b5431b304- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast