CONTINUOUS INTERNET TELEMETRY24H DRIFT12,276 material changesacross 11,592 domains · 24h to ~3h ago · +3,513 vs yesterdayNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

updiagram.com

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

This reading of updiagram.com was taken 1d ago

updiagram.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting updiagram.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 updiagram.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byZoho Mail
Secured byAmazon
Also usesGoogle Search Console
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 11:41 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 updiagram.com actually stands on - every host below is a signed observation
updiagram.com
A / AAAA
47.130.127.2918.138.112.126
unattributedserves the site
NS
ns-1482.awsdns-57.orgns-1764.awsdns-28.co.ukns-420.awsdns-52.comns-925.awsdns-51.net
awsdns-57.org + awsdns-28.co.uk + moreanswers its DNS
MX
mx.zoho.commx2.zoho.com
Zoho Mailreceives its email
TLS
updiagram.com
Amazonissued its certificate

DNS Records

A 2

  • 47.130.127.29
  • 18.138.112.126

MX 2

  • 10mx.zoho.com
  • 20mx2.zoho.com

TXT 5

  • 65citf2npkfcj9u0seqlseugdq
  • firebase=updiagram-3fd73
  • google-site-verification=8c8rkFCsoU_Y9HP8vEQAkma2nH-N5gLEMWJ_Oz9lOnE
  • google-site-verification=i-aDAb1_q0JRurN_kLT-1c2me06wpgRKL6TJoMPs7B4
  • v=spf1 include:zoho.com include:amazonses.com ~all

NS 4

  • ns-1482.awsdns-57.org
  • ns-1764.awsdns-28.co.uk
  • ns-420.awsdns-52.com
  • ns-925.awsdns-51.net

SOA 1

  • ns-420.awsdns-52.com awsdns-hostmaster.amazon.com

MCP_RECORDS 5

  • 65citf2npkfcj9u0seqlseugdq
  • firebase=updiagram-3fd73
  • google-site-verification=8c8rkFCsoU_Y9HP8vEQAkma2nH-N5gLEMWJ_Oz9lOnE
  • google-site-verification=i-aDAb1_q0JRurN_kLT-1c2me06wpgRKL6TJoMPs7B4
  • v=spf1 include:zoho.com include:amazonses.com ~all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:dmarc@updiagram.com; sp=none;

BIMI_RECORDS 5

  • 65citf2npkfcj9u0seqlseugdq
  • firebase=updiagram-3fd73
  • google-site-verification=8c8rkFCsoU_Y9HP8vEQAkma2nH-N5gLEMWJ_Oz9lOnE
  • google-site-verification=i-aDAb1_q0JRurN_kLT-1c2me06wpgRKL6TJoMPs7B4
  • v=spf1 include:zoho.com include:amazonses.com ~all

MTA_STS_RECORDS 5

  • 65citf2npkfcj9u0seqlseugdq
  • firebase=updiagram-3fd73
  • google-site-verification=8c8rkFCsoU_Y9HP8vEQAkma2nH-N5gLEMWJ_Oz9lOnE
  • google-site-verification=i-aDAb1_q0JRurN_kLT-1c2me06wpgRKL6TJoMPs7B4
  • v=spf1 include:zoho.com include:amazonses.com ~all

TLS Certificates (3)

Common NameIssuerExpires
updiagram.com C=US, O=Amazon, CN=Amazon RSA 2048 M01 Wed, 21 Oct 2026 23:59:59 +0000
Amazon RSA 2048 M01 C=US, O=Amazon, CN=Amazon Root CA 1 Fri, 23 Aug 2030 22:21:28 +0000
Amazon Root CA 1 C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Services Root Certificate Authority - G2 Thu, 31 Dec 2037 01:00:00 +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_db27c0b36c445927
Output Hash
baedf4a5ad2fda83620c463ca4287084ce7342152da8146838c5b4214ff0e5a8
Signature
ed25519:2404d4fdbb619843acb7a614feb1cf0c8c20330cfdf6675b31e67aeaa326f2e6303b703e6b365ac9f9a5739ed65fd0f3501ee6d9b45798c9623572dd4ee19809
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser