CONTINUOUS INTERNET TELEMETRY24H DRIFT25,547 material changesacross 22,819 domains · 24h to ~35m agoROTATION56 domains moved DNS from koaladns.com to kirklanddc.com, 55 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW605 curated domains not reachablelast probe, steadySITE ERRORS33,530 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,011 sites429 rate-limit / 403 bot-block, a posture signal

usechimney.com

Observed Jul 26, 2026, 02:07 UTC (13d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of usechimney.com was taken 13d ago

usechimney.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting usechimney.com 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 usechimney.com 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
Email byMicrosoft 365
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat usechimney.com actually stands on - every host below is a signed observation
usechimney.com
NS
piper.ns.cloudflare.comchance.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
usechimney-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

server_error Server error (5xx) 530 Server Error
HTTP status530
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time3,560 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

MX 1

  • 0usechimney-com.mail.protection.outlook.com

TXT 2

  • v=spf1 include:spf.protection.outlook.com include:sendgrid.net -all
  • v=DMARC1; p=reject; rua=mailto:dmarc@stormideas.uriports.com; ruf=mailto:dmarc@stormideas.uriports.com; fo=1:d:s

NS 2

  • piper.ns.cloudflare.com
  • chance.ns.cloudflare.com

SOA 1

  • chance.ns.cloudflare.com dns.cloudflare.com

TLS Certificates (0)

None.

Subdomains (5)

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_8fdbc21a18935026
Output Hash
16044e4d1039264fb4d0cf38b0ecd6affb1e216fad218940ba86dcafcb1bed0c
Signature
ed25519:ea3675cc801512cdd8e52af0d2309185e4d92e5487ff6be739781cb856e47e46aca907e5871e08b4259eee898f436f18fd73bafd3dce420569613ec9255b5400
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
Verify this in your browser