bhgmsk.cn
Observed Aug 16, 2026, 17:13 UTC (16h 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.
Steady. No change on record for bhgmsk.cn in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.
DNS Records
NS 2
ns1.julydns.comns2.julydns.com
SOA 1
ns1.julydns.com master.jmdns.com
MCP_RECORDS 1
3rkkxr08pv9j.bhgmsk.cn.eo.dnse3.com
DMARC_RECORDS 1
3rkkxr08pv9j.bhgmsk.cn.eo.dnse3.com
BIMI_RECORDS 1
3rkkxr08pv9j.bhgmsk.cn.eo.dnse3.com
MTA_STS_RECORDS 1
3rkkxr08pv9j.bhgmsk.cn.eo.dnse3.com
TLS Certificates (0)
None.
Subdomains (0)
None observed.
DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works
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_8437d1d53a61f26b- Output Hash
386ec35d09bb3b54eb110251641644cbf59a9e427a53fb16d6aa9404493dc32e- Signature
ed25519:c2e03de9a1bae45ec9634909ab87611b5648f5a1400bce3e55b2547714ba376dc5691842c6193a7fceeb9e42fd9f96cc45e5a9be8879c96ade716c4586445002- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast