CONTINUOUS INTERNET TELEMETRY24H DRIFT38,088 material changesacross 34,280 domains · last 24hDNS DRIFT53 domains changed DNS providertop destination koaladns.com · +31 vs yesterdayNOW543 curated domains not reachablelast probe, steadySITE ERRORS33,703 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,225 sites429 rate-limit / 403 bot-block, a posture signal

zi-outlook.com

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

This reading of zi-outlook.com was taken 11d ago

zi-outlook.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zi-outlook.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 zi-outlook.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
Runs onCloudflare
Secured byGoogle Trust Services
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 15:21 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 zi-outlook.com actually stands on - every host below is a signed observation
zi-outlook.com
A / AAAA
104.18.40.121172.64.147.1352a06:98c1:3105::ac40:93872a06:98c1:3107::6812:2879
Cloudflareserves the site
NS
rita.ns.cloudflare.comtim.ns.cloudflare.com
cloudflare.comanswers its DNS
TLS
zi-outlook.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 104.18.40.121
  • 172.64.147.135

AAAA 2

  • 2a06:98c1:3105::ac40:9387
  • 2a06:98c1:3107::6812:2879

MX 1

  • 0

TXT 6

  • v=spf1 -all
  • v=spf1 include:_u.zi-outlook.com._spf.smart.ondmarc.com -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all

NS 2

  • rita.ns.cloudflare.com
  • tim.ns.cloudflare.com

SOA 1

  • rita.ns.cloudflare.com dns.cloudflare.com

TLS Certificates (3)

Common NameIssuerExpires
zi-outlook.com C=US, O=Google Trust Services, CN=WE1 Sat, 12 Sep 2026 13:07:29 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 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 (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_28bafa402d10b467
Output Hash
4343df2862765a76e16da20dfef9ebf11895804c10a3a30da82a71be128b2545
Signature
ed25519:258602846bcb7f3f72f3bf75327188f90f8af1e50c85bf6e6b5ad373a67acdd545cf13c3a95bc3c98185f5814e5c7f81fc0b7bbe93d7b64e908b8b41383d4c0b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser