CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 24,136 material changesacross 23,195+ domains · 24h to ~12h ago · a floor, 12h of 24 walkedDNS DRIFT78 domains changed DNS providertop destination koaladns.com · +2 vs yesterdayNOW587 curated domains not reachable+56 vs yesterdaySITE ERRORS33,537 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,460 sites429 rate-limit / 403 bot-block, a posture signal

virginiasoap.com

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

This reading of virginiasoap.com was taken 6d ago

virginiasoap.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting virginiasoap.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 virginiasoap.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-07 08:54 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 virginiasoap.com actually stands on - every host below is a signed observation
virginiasoap.com
A / AAAA
76.223.54.14613.248.169.48
unattributedserves the site
NS
ns1.afternic.comns2.afternic.com
afternic.comanswers its DNS
TLS
virginiasoap.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 (4)

Common NameIssuerExpires
virginiasoap.com C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1 Wed, 16 Dec 2026 12:40:41 +0000
GoDaddy TLS Intermediate CA DV - R1v1 C=US, O=GoDaddy.com, CN=GoDaddy TLS Root CA - R1 Fri, 24 Aug 2040 11:59:59 +0000
GoDaddy TLS Root CA - R1 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
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_276767e378a874fe
Output Hash
ca09047ffccbe113bdbb1b7b988bef4320d8ae35cb795e9f70c6788fa54c8e4f
Signature
ed25519:5f792fabf023b53fec92b2e4ea8161500b8a40958db37e5d4eac3cf5ff5719828c0404d0c456e4ac4a631584192785faf21857989bd71110696df3b04cd97b04
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser