VirusTotal
16 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“GPT X2 iFex | Official Website Platform”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@w1n.nl.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
16 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
5 threat-system alerts
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
5 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | gptx2ifex.net |
malicious | Sinkholed |
| OpenDNS | gptx2ifex.net |
phishing | Phishing Block |
| DigiCert UltraDNS | gptx2ifex.net |
malicious | Sinkholed |
| Quad9 DNS | gptx2ifex.net |
malicious | Sinkholed |
| DNS4EU | gptx2ifex.net |
malicious | Sinkholed |
Stored narrative · generated . Provider checks below retain their own observation dates.
gptx2ifex.net returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-09, and its registration date is listed as 2026-03-26.
The HTTP check on 2026-10-01 recorded status 200 for gptx2ifex.net. The domain was first observed on 2026-09-09, while its registration date is 2026-03-26. VirusTotal recorded 16 detections across 89 scanners on 2026-09-18. OTX recorded 5 pulses on 2026-09-10. The publisher-owned PhishDestroy catalogue listed the domain, and the SSL certificate was scanned on 2026-09-09.
The HTTP, VirusTotal, OTX and PhishDestroy observations carry different dates, so comparisons between them reflect separate snapshots rather than a single moment. The earliest observation on 2026-09-09 and the latest HTTP check on 2026-10-01 bracket a period during which the recorded signals were collected. Because the dates differ, a reader should compare each source against its own timestamp instead of treating the records as simultaneous.
Retain the dated records for gptx2ifex.net so that later observations can be compared against the 2026-09-09, 2026-09-10, 2026-09-18 and 2026-10-01 snapshots. When reviewing the domain, avoid submitting sensitive information through any page associated with it. Compare any subsequent checks with the recorded values before drawing conclusions from a single observation.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
brit.ns.cloudflare.comdamiete.ns.cloudflare.comLocation describes the IP network.
1522b4a98cd8090bc5f1809784c62f7ce85bb4857d361714b54e1d614f30592fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of gptx2ifex.net · checked Sep 9, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
CaddyScanner note: alive_content: raw=short_403; http=403; via=https_proxy; server=Caddy
91.236.116.210.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
live_content→protected
http_access_restricted · access_restriction
protected→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
protected→Unknown
stale_current_evidence
Unknown→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
live_content→Unknown
probe_inconclusive
protected→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
live_content→Unknown
probe_inconclusive
protected→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
protected
http_access_restricted · access_restriction
Reachable
13 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20260909-D6DAA3 Recipient: abuse@w1n.nl Registrar: NICENIC International Group Co., Limited (Hong Kong (China)) Policy Violations: “Services may be used only for lawful purposes… fraud, abuse and illegal activity prohibited. Violations may result in immediate suspension.” + dedicated abuse handling and takedown Applicable Laws: Crimes Ordinance Cap.200 (Fraud), Theft Ordinance Cap.210 §16A (fraud by deception), Personal Data (Privacy) Ordinance Cap.486
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive