CONTINUOUS INTERNET TELEMETRY24H DRIFT48,068 material changesacross 44,346 domains · 24h to ~3h ago · +13,662 vs yesterdayROTATION53 domains moved DNS from magpiedns.com to koaladns.com, 50 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW608 curated domains not reachablelast probe, steadySITE ERRORS34,089 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,502 sites429 rate-limit / 403 bot-block, a posture signal

jobcn.com

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

This reading of jobcn.com was taken 7d ago

jobcn.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting jobcn.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 jobcn.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 onCHINANET Guangdong province network
Registered withXiamen 35.com Information Co., Ltd.
tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 07:55 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 jobcn.com actually stands on - every host below is a signed observation
jobcn.com
A / AAAA
183.61.245.68
CHINANET Guangdong province networkserves the site
NS
mist.dnspod.netantonia.dnspod.net
dnspod.netanswers its DNS
MX
mta.jobcn.commail.jobcn.com
jobcn.comreceives its email

DNS Records

A 1

  • 183.61.245.68

MX 2

  • 2mta.jobcn.com
  • 5mail.jobcn.com

TXT 1

  • v=spf1 ip4:183.61.245.64/28 a mx -all

NS 2

  • mist.dnspod.net
  • antonia.dnspod.net

SOA 1

  • mist.dnspod.net freednsadmin.dnspod.com

MCP_RECORDS 1

  • v=spf1 ip4:183.61.245.64/28 a mx -all

DMARC_RECORDS 1

  • v=spf1 ip4:183.61.245.64/28 a mx -all

BIMI_RECORDS 1

  • v=spf1 ip4:183.61.245.64/28 a mx -all

MTA_STS_RECORDS 1

  • v=spf1 ip4:183.61.245.64/28 a mx -all

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_1afc476d4f474eec
Output Hash
efaa5592666fe6d736575046a3fda84b53b4c1885c9dd83457c965325c4914a1
Signature
ed25519:3c4a02b4e8c860a39b47be6e38541d3216946e560332ea83b2ad3a1cf5602474592f5c374c2f964286513cc661b62be817778a91cf7bcd18cd6f2910ddcba703
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser