qdheshan.com returned HTTP status 200 in an HTTP check dated 2026-10-01, a recorded response that describes only that request. A PhishDestroy internal listing for the domain is also recorded, and the first observation of qdheshan.com is dated 2026-09-19.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 200. VirusTotal, checked on 2026-09-29, reported 16 detections across 91 scanners. OTX, checked on 2026-09-20, recorded 7 pulses. The domain was registered on 2026-08-23 with registrar Gname 170 Inc, and its SSL certificate, scanned on 2026-09-19, was issued by Let's Encrypt / YR2. PageSpeed, checked on 2026-09-19, recorded a performance score of 56.
Interpretation
The HTTP response, VirusTotal detections, OTX pulses, and PhishDestroy listing each describe a separate source's observation of qdheshan.com. Because these records carry different dates, they are best compared as distinct dated snapshots rather than merged into one conclusion. The chronology from first observation to the later checks shows the domain appeared across multiple source records during that period.
Recommended Actions
Preserve the HTTP check, VirusTotal, and OTX records for qdheshan.com as separate dated artifacts. Compare the PhishDestroy listing against the VirusTotal and OTX observations in separate review steps. Re-check qdheshan.com against the same sources before relying on any single record.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: HTTP access restricted50% confidence
Attributionmechanism: Access Restrictionsource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-11 10:09:12 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:09:12 UTClast content: 2026-10-11 01:42:15 UTC
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.
技术 · 4 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Google PageSpeed Insights — mobile performance audit of qdheshan.com· checked Sep 19, 2026
56
Needs Work
Performance
FCP
8.31s
First Contentful Paint
LCP
59.74s
Largest Contentful Paint
CLS
0.01
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
8.31s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-19 16:55:02 UTC
VirusTotal scanner detections updated from 14 to 15. Added scanner alerts: CyRadar.
VirusTotal Detections Update2026-09-19 13:05:45 UTC
VirusTotal scanner detections updated from 11 to 14. Added scanner alerts: Forcepoint ThreatSeeker, SOCRadar, Seclookup.
Threat First Observed2026-09-19 11:00:43 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 76.76.21.21.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(SE)
