cric-colombia.org

Observed Aug 24, 2026, 10:11 UTC (8d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of cric-colombia.org was taken 8d ago

cric-colombia.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting cric-colombia.org 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 cric-colombia.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Runs onCloudflare
Email byGoogle Workspace
Registered withCloudflare, Inc.
Also usesGoogle Search Console
IPv6 · 3 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 cric-colombia.org 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 time24 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 16

A2AAAA2NS2MX7TXT2SOA1

TLS certificates 0

None.

Subdomains 3

3 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_faa9c0caf9cedd64
Output Hash
6b5aec7f6851a81c8ca49f444f12c1c1d5ab393c5994c04d35d10d11b86caf1c
Signature
ed25519:4da5f35e610ec3761df890a18823aeaf44245a65a77d808ba558212b09892136b009c390f1aa328c7b55dc6dd8b9daf20060c9d25eed3052daa9088aa903570d
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT4,372 material changesacross 2,372 domains · 24h to ~2h ago · +187 vs yesterdayROTATION57 domains moved DNS from magpiedns.com to koaladns.com, 50 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT3 changed registrar24hNOW567 curated domains not reachablelast probe, steadySITE ERRORS18,220 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 80,832 sites429 rate-limit / 403 bot-block, a posture signal