CONTINUOUS INTERNET TELEMETRY24H DRIFT49,307 material changesacross 44,221 domains · 24h to ~2h ago · +14,901 vs yesterdayROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 55 moved backa rotation loop, not a migration · 24hNOW607 curated domains not reachablelast probe, steadySITE ERRORS34,084 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,310 sites429 rate-limit / 403 bot-block, a posture signal

valpotorch.com

Observed Jul 27, 2026, 20:07 UTC (13d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of valpotorch.com was taken 13d ago

valpotorch.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting valpotorch.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 valpotorch.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured byGoogle Trust Services
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 22:42 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 valpotorch.com actually stands on - every host below is a signed observation
valpotorch.com
A / AAAA
192.104.183.209192.104.183.109
unattributedserves the site
NS
dns2.tn-cloud.netdns1.tn-cloud.net
tn-cloud.netanswers its DNS
MX
mail.valpotorch.com
valpotorch.comreceives its email
TLS
valpotorch.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.104.183.209
  • 192.104.183.109

MX 1

  • 10mail.valpotorch.com

TXT 5

  • v=spf1 mx include:tn-cloud.net -all
  • v=DMARC1; p=none
  • v=spf1 mx include:tn-cloud.net -all
  • v=spf1 mx include:tn-cloud.net -all
  • v=spf1 mx include:tn-cloud.net -all

NS 2

  • dns2.tn-cloud.net
  • dns1.tn-cloud.net

SOA 1

  • dns1.tn-cloud.net list_dnsadmin.tn-cloud.net

TLS Certificates (3)

Common NameIssuerExpires
valpotorch.com C=US, O=Google Trust Services, CN=WR1 Wed, 14 Oct 2026 17:17:01 +0000
WR1 C=US, O=Google Trust Services LLC, CN=GTS Root R1 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R1 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

Subdomains (1)

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_2f2a79dea3c9bedb
Output Hash
96a8145c7af6b611eea03f499f5faa7de6685b97c7825345815a3edc246d9095
Signature
ed25519:bbccc2498410dcfdf6d303b5a73c8720d8e9812627562f3d9213f670f3004235ba445cb5ec77bb689c00c5f770f673c8e9c9541e4b503650c3b23591dc7ad40d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser