cctvbestservices.com

Observed Aug 20, 2026, 14:32 UTC (6h 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.

Not responding
Runs onCloudflare
Registered withGoDaddy.com, LLC
IPv6 · 1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for cctvbestservices.com 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

Timed out No response within the timeout Connection timed out - no response within 3s
HTTP status0
Servernot observed
TLS protocolnot observed
TLS issuernot observed
Behind Cloudflareno
Time spent waiting6,200 ms (2 attempts, 3s each) - nothing answered
DNS resolutionNOERROR
What this reading means

Nothing answered on 443 inside our budget: 2 attempts of 3s each, from Cloudflare's network. DNS resolved, so the name and its delegation are fine - the failure is below that, at the connection or HTTP layer.

It does NOT mean the site is down for everyone. Our budget is deliberately tight so a two-million-domain sweep stays affordable, and a site that is merely slow will miss it while working fine in a browser.

Probed from Cloudflare's network. A site can be healthy and still not answer us: use the live checks on the domain page to run the same probe from your own network and compare.

What produces this, in rough order of how often
  • The origin takes longer than 3s to send its first byte - real users see this as a slow site, not a broken one.
  • A firewall DROPS our packets rather than refusing them. A refusal would have come back as "connection refused"; silence is what a drop rule looks like from outside.
  • Traffic from datacenter or cloud networks is filtered. We egress from Cloudflare, which many origins treat differently from a residential connection.
  • An AAAA record is published for an address that is not actually serving, so clients that prefer IPv6 hang.
  • The origin only answers browser-like requests. We identify ourselves as DomainDrift rather than impersonating a browser.

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 7

A2AAAA2NS2SOA1

TLS certificates 0

None.

Subdomains 1

1 subdomain hostname 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_4d7d39a6c9569d9b
Output Hash
6da68d617d4ee9d1658584e85708502712198039eacda53d0297b31aad088ad6
Signature
ed25519:18c0f0b569ec220b4a3d942700674b30815076003b54b1653b486c2c205a2c2dfa4d1da6ee328d4c57366a7c5c71dbbcf7e9d7bcf60f916e0b1079ab285ea402
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT12,679 material changesacross 10,593 domains · 24h to ~17h ago · +6,017 vs yesterdayROTATION74 domains moved DNS from kirklanddc.com to koaladns.com, 71 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT4 changed registrar24hNOW184 curated domains not reachable+64 vs yesterdaySITE ERRORS17,775 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 77,934 sites429 rate-limit / 403 bot-block, a posture signal