On 2026-10-01, an HTTP check of baddestkid.com returned status 502, a recorded gateway response rather than a page. The domain was first observed on 2026-09-08, roughly a month before that check, and its registration date is 2026-09-07.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 502 for baddestkid.com, while the domain's first observation was logged on 2026-09-08. VirusTotal, checked on 2026-09-17, reported 3 detections across 89 scanners. OTX, also checked on 2026-09-17, listed 3 pulses. The domain appears in the PhishDestroy internal listing, and its registrar is Dominet (HK) Limited, with registration dated 2026-09-07. The resolving IP is 104.21.85.34, in the US, under AS13335 Cloudflare, Inc.
Interpretation
The dated records describe separate measurements: an HTTP response, a VirusTotal scan, an OTX pulse count, and a publisher-owned listing. Because these sources were checked on different dates, their figures should be read individually rather than combined into a single trend. The registration and first-observation dates fall close together, which places the earliest recorded activity shortly after registration.
Recommended Actions
Preserve the baddestkid.com records from VirusTotal, OTX, and the PhishDestroy listing for later comparison. Compare the HTTP response record against future checks of the same domain, and review the VirusTotal and OTX entries separately rather than merging their figures. Re-check the domain's recorded status before relying on any single dated observation.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='baddestkid.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Trezor Suite App (Official) | Desktop & Web Crypto Management | Trezor
TLS 证书
Hostname coverage not recorded·
颁发者 WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.85.34
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP 声誉不属于此域。
域名服务器 1
mina.ns.cloudflare.com
Location describes the IP network.
TLS 证书
Issuer
WE1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:15:53 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-08 05:28:07 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-08 05:28:07 UTC → 2026-09-30 16:14:55 UTC · 538.78hmidpoint estimate ≈ 2026-09-19 10:51:31 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed First positive detection Previous stored snapshot: 3 detections
alphaMountain.ai
Gridinsoft
SOCRadar
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-17 19:10:17 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: SOCRadar.
Domain Status Transition2026-09-15 22:00:20 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 20:23:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(HK)
