jaring.my
Observed Aug 16, 2026, 16:07 UTC (12h 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 jaring.my 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
A 1
183.81.162.32
MX 1
10mbox-vs01.jaring.asia
TXT 1
v=spf1 include:spf.jaring.asia -all
NS 2
pdns1.ipserverone.compdns2.ipserverone.com
SOA 1
pdns1.ipserverone.com support.ipserverone.com
MCP_RECORDS 1
v=spf1 include:spf.jaring.asia -all
DMARC_RECORDS 1
v=spf1 include:spf.jaring.asia -all
BIMI_RECORDS 1
v=spf1 include:spf.jaring.asia -all
MTA_STS_RECORDS 1
v=spf1 include:spf.jaring.asia -all
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_6826f6d22df355de- Output Hash
66d847e31bb500ae948f87c476695e117384b3a274c9614d151cebd1c9b03247- Signature
ed25519:0a0b521f35ac8f821b576562548dd7022b9871f89bc5c7c82b6d87314c940e2ed3807ec27a8743a8073bbca41e1ab0d094650105b9b19682a05314b2ab47a209- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast