CONTINUOUS INTERNET TELEMETRY24H DRIFT43,686 material changesacross 39,414 domains · 24h to ~45m ago · +9,069 vs yesterdaySHIFT37 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW542 curated domains not reachablelast probe, steadySITE ERRORS33,822 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 151,367 sites429 rate-limit / 403 bot-block, a posture signal

vidto.me

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

This reading of vidto.me was taken 3d ago

vidto.me is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vidto.me 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 vidto.me 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 byLet's Encrypt
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 21:31 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 vidto.me actually stands on - every host below is a signed observation
vidto.me
A / AAAA
103.224.182.253
unattributedserves the site
NS
ns2.abovedomains.comns1.abovedomains.com
abovedomains.comanswers its DNS
MX
alltheemails.com
alltheemails.comreceives its email
TLS
vidto.me
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.253

MX 1

  • 10alltheemails.com

TXT 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

NS 2

  • ns2.abovedomains.com
  • ns1.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

MCP_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

DMARC_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

BIMI_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

MTA_STS_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

TLS Certificates (3)

Common NameIssuerExpires
vidto.me C=US, O=Let's Encrypt, CN=YR1 Mon, 19 Oct 2026 14:05:26 +0000
YR1 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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_13c47607a6bd7009
Output Hash
8ba2b655d72f484405a1104e0ade89775c9b7c2ce212d6b8c468d360ceaee110
Signature
ed25519:732bc777c2ac934e3110117095680f4ff7fd7977313ab2853c5904a4196bf030dd02269582f437645b8cd5972505738958aa721f56df90bd1e1d0892e4a1a10c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser