3456.app
Observed Aug 25, 2026, 23:21 UTC (2h 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.
CloudflareSteady. No change on record for 3456.app 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 4
TLS certificates 0
None.
Subdomains 96
96 subdomain hostnames observed and signed - the list itself is part of the paid record.
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_000bca0e4b457330- Output Hash
7549049492ffe6940116e80cce3d2882ebf45302392f9692f44c78eac0b2e2a3- Signature
ed25519:9b8c64be10cbb7e77184d6f1185fc17fd2fd1decb4489d76c99ab8190780ef1a92c50a6c9a0910e403c1368af77a664872f904f9680e06eb3d6ef5c515a7900f- Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff- Parent
(genesis)- Plane
- fast