runswith.dns.drm3.network
Last scanned 10m ago; the signed record is unchanged since 8d ago. Every field below carries an Ed25519 signature from that last reading. Catalog observation, re-checked on rotation - watch it for 5-minute checks.
CloudflareSteady. No change on record for runswith.dns.drm3.network 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.
HTTPS probe
The site answered with a 5xx, so the edge and TLS are working and the application behind them is not.
It does NOT mean the domain or its DNS is misconfigured - the request got all the way to an application to fail there.
- The origin is erroring or mid-deploy.
- An upstream in front of the origin cannot reach it.
These are the known causes, not a diagnosis of this domain. We recorded that nothing answered; we did not measure why.
Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".
DNS records 0
No DNS records observed. The resolver answered EMPTY - this reading records an absence, and it is signed like any other.
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 receiptthe raw cryptographic proof
- Receipt ID
rcpt_108efe2cbae12a67- Output Hash
5961dcb4c5770e38c86c82e0c328ac0e4cfc3bb6a64fb3ff78fac47fe6bb7d5a- Signature
ed25519:f1e7d51936c6f28d87deab5d14f363a0db0bba8ef44b3b77376af5bd3af3685732310b1c21944cef034529a2be5dfcfda2a23a1525821f6e6d8a9b5eaa4b2102- Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff- Parent
(genesis)- Plane
- fast