SSL certificate is invalid or expired. Issuer: R10
证据摘要
关键
VirusTotal
11/91
URLScan
Stored capture
The domain qfs.trustyheritage.online was registered on February 21, 2026 and is currently classified as a high‑risk, active brand‑impersonation site. The threat is identified with seed 609a50 and is associated with the generic “across” brand target, meaning the page attempts to masquerade as multiple well‑known services. The page title returned by the server is “QFS - Your Site”.
Infrastructure analysis shows the domain resolves to IP 163.61.188.5, which is announced by AS153568 (NEW DHAKA HARDWARE) and geolocated in the United States. The authoritative name servers are cdns1.interserver.net, cdns2.interserver.net, and cdns3.interserver.net, all of which are commonly used by hosting providers. The SSL certificate is rated R10, indicating a low‑trust issuance.
Detection telemetry indicates that VirusTotal has flagged the domain on 1 of 95 scanned security vendors, and Gridinsoft assigns a trust score of 0 out of 100. The domain appears on a single external blocklist and is actively blocked by the PhishDestroy feed. An HTTP GET returns status code 200, confirming that the site is serving content despite the low trust signals.
Defenders should treat qfs.trustyheritage.online as malicious and enforce block rules at the DNS and proxy layers. Continuous monitoring of the associated IP address and the three Interserver name servers is advised, as they may host additional impersonation sites. Incident response teams should collect the page content, TLS certificate chain, and any observed client interactions for further forensic analysis.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='qfs.trustyheritage.online', port=80): Max retries exceeded with url: / (Caused by NewConne
For the registrable domain trustyheritage.online behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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:03 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-08-22 22:15:41 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-22 22:15:41 UTC → 2026-09-30 16:14:55 UTC · 929.99hmidpoint estimate ≈ 2026-09-11 07:15:18 UTC · precision very 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 Previous stored snapshot: 13 detections
BitDefender
Chong Lua Dao
CRDF
CyRadar
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
SOCRadar
Sophos
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.
Domain Status Transition2026-08-09 22:13:58 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-08-09 10:17:51 UTC
Domain state transitioned from alive to dead.
威胁响应 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.
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.
(US)
