bjjfsd.com

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

This reading of bjjfsd.com was taken 5d ago

bjjfsd.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bjjfsd.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 bjjfsd.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Runs onHangzhou Alibaba Advertising
Registered withAlibaba Cloud Computing (Beijing) Co., Ltd.
Also usesGoogle Search Console
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 16:25 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 bjjfsd.com actually stands on - every host below is a signed observation
bjjfsd.com
A / AAAA
47.96.98.63
Hangzhou Alibaba Advertisingserves the site
NS
dns27.hichina.comdns28.hichina.com
hichina.comanswers its DNS
MX
qiye163mx01.mxmail.netease.comqiye163mx02.mxmail.netease.com
netease.comreceives its email

DNS Records

A 1

  • 47.96.98.63

MX 2

  • 5qiye163mx01.mxmail.netease.com
  • 10qiye163mx02.mxmail.netease.com

TXT 3

  • google-site-verification=KsDRN_SSi6GGjnfn471lgJOCN8D0rFvnNJiTM1ASCQs
  • v=spf1 include:spf.163.com -all
  • v=DMARC1; p=none; fo=1; ruf=mailto:dmarc@qiye.163.com; rua=mailto:dmarc_report@qiye.163.com

CNAME 1

  • bjjfsd.cn

NS 2

  • dns27.hichina.com
  • dns28.hichina.com

SOA 1

  • dns27.hichina.com hostmaster.hichina.com

MCP_RECORDS 1

  • v=spf1 include:spf.mail.faidns.com ~all

DMARC_RECORDS 1

  • v=DMARC1; p=quarantine; fo=1; ruf=mailto:dmarc@qiye.163.com; rua=mailto:dmarc_report@qiye.163.com

BIMI_RECORDS 1

  • v=spf1 include:spf.mail.faidns.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:spf.mail.faidns.com ~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_902c6fa17ee91c32
Output Hash
9feb0ed1b72f625864eb1c8aaf108ac5a0e00dcc03740fe00f58131437adcf02
Signature
ed25519:c21a1f68a5fc05b076deaec1c5ab5b69f07ce5fce65b81987ef53a07e6326733eec8122419c928cacd738c26132a2c6ab27f2f6e3f73c68ecd1031bc2f723c09
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT45,283 material changesacross 43,517 domains · 24h to ~60m ago · +1,201 vs yesterdayROTATION55 domains moved DNS from koaladns.com to magpiedns.com, 55 moved backa rotation loop, not a migration · 24hNOW494 curated domains not reachablelast probe, steadySITE ERRORS36,540 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,613 sites429 rate-limit / 403 bot-block, a posture signal