mirageforums.net

Observed Sep 1, 2026, 05:52 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.

Guarded by a firewall
Runs onCloudflare
Registered withGoDaddy.com, LLC
DNSSEC on · 2 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for mirageforums.net 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

Bot-blocked Blocked our probe (WAF / bot protection) 403 blocked by cloudflare - bot protection active
HTTP status403
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time151 ms
DNS resolutionNOERROR
What this reading means

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.

What produces this, in rough order of how often
  • 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".

SIGNED-OUT VIEW Provider names, posture and counts are shown. The record values - every DNS answer, each subdomain hostname, raw TXT, IPs, cert names and WHOIS - are the product. Sign in for the full signed record, or use the API with a key.

DNS records 8

A2NS2MX1TXT2SOA1

TLS certificates 0

None.

Subdomains 2

2 subdomain hostnames observed and signed - the list itself is part of the paid record.

The proof

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 receipt
Ed25519 receiptthe raw cryptographic proof
Receipt ID
rcpt_9d2207cf3164a055
Output Hash
5512fd3aa5fc908692cbd6be5e5c89717c350a040c2afe3c3f99f00bb641fec1
Signature
ed25519:1144142019db9fc63bdd159ec07fd651df890f5264459571655c3c6f321b83c6ff027658477fa78203d958a673293b67c7e4bde0608912668fe69d00628c030e
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT5,550 material changesacross 3,559 domains · 24h to ~3h ago · +1,365 vs yesterdayROTATION61 domains moved DNS from koaladns.com to magpiedns.com, 52 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW582 curated domains not reachablelast probe, steadySITE ERRORS18,222 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 80,759 sites429 rate-limit / 403 bot-block, a posture signal