CONTINUOUS INTERNET TELEMETRY24H DRIFT31,041 material changesacross 29,568 domains · 24h to ~75m agoSHIFT23 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW563 curated domains not reachablelast probe, steadySITE ERRORS34,155 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,271 sites429 rate-limit / 403 bot-block, a posture signal

uploadingit.com

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

This reading of uploadingit.com was taken 1d ago

uploadingit.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting uploadingit.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 uploadingit.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured byGoDaddy.com
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 19:31 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 uploadingit.com actually stands on - every host below is a signed observation
uploadingit.com
A / AAAA
13.248.169.4876.223.54.146
unattributedserves the site
NS
ns1.namefind.comns2.namefind.com
namefind.comanswers its DNS
TLS
uploadingit.com
GoDaddy.comissued its certificate

DNS Records

A 2

  • 13.248.169.48
  • 76.223.54.146

TXT 1

  • v=spf1 -all

NS 2

  • ns1.namefind.com
  • ns2.namefind.com

SOA 1

  • ns1.namefind.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (4)

Common NameIssuerExpires
uploadingit.com C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1 Thu, 19 Nov 2026 16:24:27 +0000
GoDaddy TLS Intermediate CA DV - R1v1 C=US, O=GoDaddy.com, CN=GoDaddy TLS Root CA - R1 Fri, 24 Aug 2040 11:59:59 +0000
GoDaddy TLS Root CA - R1 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +0000
Go Daddy Root Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_806b8d657cc61b7e
Output Hash
6be5ccea9d3beb6a4bbf344e9070c86bbb10409e414a64bc1d6d4507504c3124
Signature
ed25519:d520bb9a2d3a42c4d49385c3a20bcc5a0efb9c34a83dcbfec0408d7263f8c61be3086b6ac658e05acbcca180c1d20236c6eb6ed144e457da57cd7c0a10e4840b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser