CONTINUOUS INTERNET TELEMETRY24H DRIFT25,547 material changesacross 22,819 domains · last 24hROTATION56 domains moved DNS from koaladns.com to kirklanddc.com, 54 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW603 curated domains not reachablelast probe, steadySITE ERRORS33,533 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,101 sites429 rate-limit / 403 bot-block, a posture signal

dsdtech-global.com

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

This reading of dsdtech-global.com was taken 6d ago

dsdtech-global.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting dsdtech-global.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 dsdtech-global.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 21:01 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 dsdtech-global.com actually stands on - every host below is a signed observation
dsdtech-global.com
A / AAAA
103.224.182.244
unattributedserves the site
NS
ns1.abovedomains.comns2.abovedomains.com
abovedomains.comanswers its DNS
MX
park-mx.above.com
above.comreceives its email
TLS
nvgtube.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.244

MX 1

  • 10park-mx.above.com

TXT 1

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

NS 2

  • ns1.abovedomains.com
  • ns2.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
nvgtube.com C=US, O=Let's Encrypt, CN=YR2 Tue, 06 Oct 2026 02:17:14 +0000
YR2 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_2e9e1cb1e474eccd
Output Hash
d15db7f52dfaf0a6c3d0ba1cae9dd58a3e6d8b8e4aec331042b43107e079d030
Signature
ed25519:b6c5d7ac4ba38781ba5fe2dd24b8c753e395aab05235446d86a3391dc596232d64c36566d3e62970d24ba926ddfcff1a78cc296f6753bba895981eda61725107
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser