CONTINUOUS INTERNET TELEMETRY24H DRIFT62,563 material changesacross 59,341 domains · 24h to ~2h ago · +27,946 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW535 curated domains not reachablelast probe, steadySITE ERRORS33,826 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 129,659 sites429 rate-limit / 403 bot-block, a posture signal

villaggioqatar.com

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

This reading of villaggioqatar.com was taken 3d ago

villaggioqatar.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting villaggioqatar.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 villaggioqatar.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Email byMicrosoft 365
Also usesGoogle Search Console
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 07:56 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 villaggioqatar.com actually stands on - every host below is a signed observation
villaggioqatar.com
A / AAAA
13.234.89.121
unattributedserves the site
NS
ns31.worldnic.comns32.worldnic.com
worldnic.comanswers its DNS
MX
villaggioqatar-com.mail.protection.outlook.com
Microsoft 365receives its email

DNS Records

A 1

  • 13.234.89.121

MX 1

  • 0villaggioqatar-com.mail.protection.outlook.com

TXT 3

  • v=spf1 ip4:212.70.100.10 include:spf.protection.outlook.com ~all
  • MS=ms19024693
  • google-site-verification=f6L4PGLUZh1nqR2fogqXirZk1B4i81Q92sE2EaxZW7U

NS 2

  • ns31.worldnic.com
  • ns32.worldnic.com

SOA 1

  • NS31.WORLDNIC.com namehost.WORLDNIC.com

MCP_RECORDS 1

  • google-site-verification=f6L4PGLUZh1nqR2fogqXirZk1B4i81Q92sE2EaxZW7U

DMARC_RECORDS 1

  • v=DMARC1;p=reject

BIMI_RECORDS 1

  • google-site-verification=f6L4PGLUZh1nqR2fogqXirZk1B4i81Q92sE2EaxZW7U

MTA_STS_RECORDS 1

  • google-site-verification=f6L4PGLUZh1nqR2fogqXirZk1B4i81Q92sE2EaxZW7U

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