CONTINUOUS INTERNET TELEMETRY24H DRIFT51,574 material changesacross 48,279 domains · 24h to ~3h ago · -10,502 vs yesterdayROTATION52 domains moved DNS from magpiedns.com to koaladns.com, 52 moved backa rotation loop, not a migration · 24hNOW532 curated domains not reachablelast probe, steadySITE ERRORS33,864 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 120,840 sites429 rate-limit / 403 bot-block, a posture signal

rticonnect.com

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

This reading of rticonnect.com was taken 4d ago

rticonnect.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting rticonnect.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 rticonnect.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoDaddy.com
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 17:59 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 rticonnect.com actually stands on - every host below is a signed observation
rticonnect.com
A / AAAA
76.223.54.14613.248.169.48
unattributedserves the site
NS
ns1.afternic.comns2.afternic.com
afternic.comanswers its DNS
TLS
rticonnect.com
GoDaddy.comissued its certificate

DNS Records

A 2

  • 76.223.54.146
  • 13.248.169.48

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • ns1.afternic.com
  • ns2.afternic.com

SOA 1

  • ns1.afternic.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (3)

Common NameIssuerExpires
rticonnect.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, 19 Aug 2026 16:18:09 +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, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +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_b43c7f44bbca80ed
Output Hash
5a95c742c0834c5a75dbec48a4ba85aa868ffc657273f98ebb0b412db49c4348
Signature
ed25519:33f63ed40fa9ca31e4d3eb370dd15597a282d90cabe9141f82932187828ca566f99601299707ae4c964b968b690abec3cd50d77a1c8c735e5b952bc4a2cd5d05
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser