74d.buzz
Observed Aug 24, 2026, 21:03 UTC (20h 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 74d.buzz 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
A security layer answered instead of the site. That is a working defence doing its job, and we record it as its own state rather than as a failure.
It does NOT mean the site is down or misconfigured. It also does not mean we were treated as hostile - most rules of this kind refuse every non-browser client alike.
- A WAF or bot-management rule refuses non-browser user agents by default.
- Automated traffic from datacenter networks is challenged as a matter of policy.
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 7
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_16483dbf4a419a86- Output Hash
d91fe2ae1284f55fadb7833ab25dba4bd386c69c3745aaff8563faea680c6d95- Signature
ed25519:e0f710aaa41147c2708791dbfb8fc1a8b73590b6ae1eb8b8cf6231bacf612ae4b6b7ee572f2147a51308334466ac682637fa4c5627c37ce6896810079dfee10b- Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff- Parent
(genesis)- Plane
- fast