react.tokyo
Observed Aug 12, 2026, 03:59 UTC (6d ago). Every field below was attested with an Ed25519 signature at scan time.
react.tokyo is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting react.tokyo under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.
Watch react.tokyo Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Google WorkspaceSteady. No change on record for react.tokyo 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
49.212.235.182
MX 5
1ASPMX.L.GOOGLE.COM5ALT2.ASPMX.L.GOOGLE.COM5ALT1.ASPMX.L.GOOGLE.COM10ASPMX2.GOOGLEMAIL.COM10ASPMX3.GOOGLEMAIL.COM
TXT 1
txt @ v=spf1 include:aspmx.googlemail.com ~all
NS 2
ns1.value-domain.comns2.value-domain.com
SOA 1
ns1.value-domain.com hostmaster.react.tokyo
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; the only network request the check makes is for the published public keys.
Verify this receiptEd25519 Receipt
- Receipt ID
rcpt_2c9cb2faafe0bbd6- Output Hash
17a8f07b00b888c12d2b9e941d7e67950d387fcf2b8f89f9c07f25c1f507a355- Signature
ed25519:d07e5a0753311819490620d52d09ae8e4b00feee5b85aba16396250f5d5d297a224c371609ffe5ffd71f1365efdc01d345bf222f40d2dd6b04f13d3c32946e09- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast