CONTINUOUS INTERNET TELEMETRY24H DRIFT33,450 material changesacross 32,285 domains · 24h to ~11h ago · -4,572 vs yesterdayROTATION57 domains moved DNS from kirklanddc.com to koaladns.com, 54 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW552 curated domains not reachablelast probe, steadySITE ERRORS33,805 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,647 sites429 rate-limit / 403 bot-block, a posture signal

libertycr.com

Observed Aug 2, 2026, 21:03 UTC (4d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of libertycr.com was taken 4d ago

libertycr.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting libertycr.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 libertycr.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Email byMicrosoft 365
Secured byGoDaddy.com
Registered withGoDaddy.com, LLC
Also usesFacebook/MetaGoogle Search ConsoleAtlassianFigma
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 01:06 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat libertycr.com actually stands on - every host below is a signed observation
libertycr.com
A / AAAA
104.18.30.45104.18.31.452606:4700::6812:1e2d2606:4700::6812:1f2d
Cloudflareserves the site
NS
emerson.ns.cloudflare.comelisabeth.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
libertycr-com.mail.protection.outlook.com
Microsoft 365receives its email
TLS
*.libertycr.com
GoDaddy.comissued its certificate

DNS Records

A 2

  • 104.18.30.45
  • 104.18.31.45

AAAA 2

  • 2606:4700::6812:1e2d
  • 2606:4700::6812:1f2d

MX 1

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

TXT 22

  • MS=ms52076623
  • 1f4opfd13md6v6j0bbmi3rq5nh
  • 768stnqop9nggsv9nf25g6tlvi
  • hsame3j07oavud11c37v2arlug
  • m2iju26c09judb28s62p3cud5b
  • oltkdiqlhbs8qbplo4dcb3vl01
  • Sendinblue-code:a29238386d84539fb09b8d7e6f81d8be
  • knowbe4-site-verification=1bd096acf31c5c0f5c77411d65d2b4b2
  • knowbe4-site-verification=7cb2a978a3fcdc4bba9c68e0cc98ed25
  • facebook-domain-verification=j1un7j2u0d84hd6yiq1aubrd6k3ugf

NS 2

  • emerson.ns.cloudflare.com
  • elisabeth.ns.cloudflare.com

SOA 1

  • elisabeth.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • globalsign-domain-verification=B439FEC5CE8E24AA75F210D5C3FFDDEC

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email

BIMI_RECORDS 1

  • globalsign-domain-verification=B439FEC5CE8E24AA75F210D5C3FFDDEC

MTA_STS_RECORDS 1

  • v=STSv1; id=20260720151057Z;

TLS Certificates (3)

Common NameIssuerExpires
*.libertycr.com C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., 2.5.4.11=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2 Wed, 07 Oct 2026 18:44:59 +0000
Go Daddy Secure Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Sat, 03 May 2031 07:00:00 +0000
Go Daddy Root Certificate Authority - G2 C=US, O=The Go Daddy Group, Inc., 2.5.4.11=Go Daddy Class 2 Certification Authority Fri, 30 May 2031 07:00:00 +0000

Subdomains (0)

None observed.

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_b231e7c09518880c
Output Hash
10b67f4aac1054d7af325ce2bc5b231735244bff80c55156c6fde08ae337074d
Signature
ed25519:ba34def4faad7ebaebc5c8eac7e01b2618c7ad765b8ee68aad6d0c1539cb122687b4ce1e234202f4b5aba4a064ac51fb3e6e1ce7962751cfb6ddef0e4d02830e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser