CONTINUOUS INTERNET TELEMETRY24H DRIFT52,645 material changesacross 46,755 domains · 24h to ~2h ago · +18,239 vs yesterdayROTATION53 domains moved DNS from magpiedns.com to koaladns.com, 50 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW609 curated domains not reachablelast probe, steadySITE ERRORS34,073 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,296 sites429 rate-limit / 403 bot-block, a posture signal

ghostery.net

Observed Jul 24, 2026, 19:04 UTC (16d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of ghostery.net was taken 16d ago

ghostery.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ghostery.net 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 ghostery.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Runs onAmazon
Registered withAmazon Registrar, Inc.
tranco_10k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat ghostery.net actually stands on - every host below is a signed observation
ghostery.net
A / AAAA
18.160.143.7618.160.143.5318.160.143.9818.160.143.123
Amazonserves the site
NS
ns-817.awsdns-38.netns-1481.awsdns-57.orgns-1976.awsdns-55.co.ukns-231.awsdns-28.com
awsdns-38.net + awsdns-57.org + moreanswers its DNS

HTTPS probe

server_error Server error (5xx) 525 Server Error
HTTP status525
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time492 ms
DNS resolutionNOERROR
What this reading means

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.

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

A 4

  • 18.160.143.76
  • 18.160.143.53
  • 18.160.143.98
  • 18.160.143.123

NS 4

  • ns-817.awsdns-38.net
  • ns-1481.awsdns-57.org
  • ns-1976.awsdns-55.co.uk
  • ns-231.awsdns-28.com

SOA 1

  • ns-231.awsdns-28.com awsdns-hostmaster.amazon.com

TLS Certificates (0)

None.

Subdomains (3)

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 Receipt

Receipt ID
rcpt_e915cf327939d496
Output Hash
afb7238fe45316e936995b2c0470b9a8fcde793df0e7210d667fb9c88989ce66
Signature
ed25519:c94fefe640f550b5d6bd803ac710e2159abd30b85c5cf0ba069a73f68fe3c47911c57dd4cdaf3d6007a2f7a55211ac0d48c0a0455dec9c436274e4319f325a05
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
Verify this in your browser