SSL certificate is invalid or expired. Issuer: R10
Evidence Summary
Critical
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.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note: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
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Registration (base domain)trustyheritage.online · Created Feb 21, 2026 (234d)
Time to First Unavailability33 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedFeb 26, 2026
DOM Analysisanalyzed Mar 24, 2026score 80/1004 brand signals
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
163.61.188.5
Network ASN
AS153568
Organization
NEW DHAKA HARDWARE
Observed location
New York City, US
Server header
LiteSpeed
Nameservers 1
cdns3.interserver.net
Location describes the IP network.
TLS certificate
Issuer
R10
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 inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:15:03 UTC
RDAP registrationUnknown
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
Kaspersky
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.
Threat Response Pipeline
Discovery
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
qfs.trustyheritage.online detected and queued for full analysis
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Aug 9, 2026
Time to First Unavailability
802 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
3 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · qfs.trustyheritage.online
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches2
Same favicon hash or the same page title as this host.
(US)
