CONTINUOUS INTERNET TELEMETRY24H DRIFT8,763 material changesacross 8,372 domains · 24h to ~2h ago · -32,097 vs yesterdayNOW563 curated domains not reachablelast probe, steadySITE ERRORS34,264 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,299 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

vals.ch

Observed Aug 2, 2026, 16:42 UTC (7h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Verify this receipt yourself + Watch this domain
Up right now
Email byMicrosoft 365
Secured byLet's Encrypt
Also usesGoogle Search Console
IPv6 · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 16: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 vals.ch actually stands on - every host below is a signed observation
vals.ch
A / AAAA
217.26.53.2222a00:d70:0:b:2002:0:d91a:35de
2a00serves the site
NS
ns.hostpoint.chns2.hostpoint.chns3.hostpoint.ch
hostpoint.chanswers its DNS
MX
vals-ch.mail.protection.outlook.com
Microsoft 365receives its email
TLS
vals.ch
Let's Encryptissued its certificate

DNS Records

A 1

  • 217.26.53.222

AAAA 1

  • 2a00:d70:0:b:2002:0:d91a:35de

MX 1

  • 0vals-ch.mail.protection.outlook.com

TXT 3

  • google-site-verification=LvHbhgwWbNUh4gFIKcRi_kqvABVGlFHhPnYyAAquJFU
  • google-site-verification=qi9Xy_t7R82SKB-a_tibCeBVJK7Cfhzdz4mcSu-bE0A
  • v=spf1 include:sendgrid.net include:_spf.mlsend.com include:egeko.ch include:spf.protection.outlook.com -all

NS 3

  • ns.hostpoint.ch
  • ns2.hostpoint.ch
  • ns3.hostpoint.ch

SOA 1

  • ns.hostpoint.ch hostmaster.hostpoint.ch

MCP_RECORDS 1

  • BKhyJpY68mMN89ZLeTK6Rx7D8IzEt-YYJKIpE14te3U

DMARC_RECORDS 1

  • v=DMARC1; p=none

BIMI_RECORDS 1

  • BKhyJpY68mMN89ZLeTK6Rx7D8IzEt-YYJKIpE14te3U

MTA_STS_RECORDS 1

  • BKhyJpY68mMN89ZLeTK6Rx7D8IzEt-YYJKIpE14te3U

TLS Certificates (3)

Common NameIssuerExpires
vals.ch C=US, O=Let's Encrypt, CN=YR2 Tue, 13 Oct 2026 20:53:04 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_8f48cc7ecc94e35e
Output Hash
b46cc0c24e9047f3c8a37ee9780799b9c07411afb38e9a1e4de171d399a94d24
Signature
ed25519:a261806b1afa82d711b24dd1abc61b1955a326339f63e9d9eca7f3dddf07af3c2f6f78c66b01aee532a55e37c1fc8176603d63e597b0f6a5406ad25be3232e03
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser