CONTINUOUS INTERNET TELEMETRY24H DRIFT41,685 material changesacross 38,305 domains · 24h to ~2h ago · +7,068 vs yesterdaySHIFT42 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW539 curated domains not reachablelast probe, steadySITE ERRORS33,856 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 149,215 sites429 rate-limit / 403 bot-block, a posture signal

vedekon.net

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

This reading of vedekon.net was taken 3d ago

vedekon.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vedekon.net 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 vedekon.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 21:48 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 vedekon.net actually stands on - every host below is a signed observation
vedekon.net
A / AAAA
195.10.210.16
unattributedserves the site
NS
ns2.vedekon.netns.vedekon.netnocdns.vedekon.infonocdns.vedekon.net
vedekon.net + vedekon.infoanswers its DNS
MX
mail.vedekon.netmail.vedekon.netmail2.itsupport.kiev.ua
vedekon.net + kiev.uareceives its email

DNS Records

A 1

  • 195.10.210.16

MX 3

  • 10mail.vedekon.net
  • 20mail.vedekon.net
  • 40mail2.itsupport.kiev.ua

TXT 2

  • v=spf1 a mx ip4:91.196.121.49 ip4:91.196.121.24 ip4:91.196.121.75 ip4:91.196.120.1 ~all
  • mailconf=https://autoconfig.vedekon.net/mail/config-v1.1.xml

NS 4

  • ns2.vedekon.net
  • ns.vedekon.net
  • nocdns.vedekon.info
  • nocdns.vedekon.net

SOA 1

  • ns.vedekon.net noc.vedekon.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; pct=100; adkim=s; aspf=s; sp=reject; rua=mailto:hostmaster@vedekon.net

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=STSv1; id=2026041101;

TLS Certificates (0)

None.

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