VirusTotal
15 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
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.
15 / 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.
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 | eoxphy.com |
malicious | Sinkholed |
| OpenDNS | eoxphy.com |
phishing | Phishing Block |
| DNS4EU | eoxphy.com |
malicious | Sinkholed |
| DigiCert UltraDNS | eoxphy.com |
malicious | Sinkholed |
| Quad9 DNS | eoxphy.com |
malicious | Sinkholed |
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
On 2026-10-01, eoxphy.com returned an HTTP status code of 200, according to a recorded observation. The domain's registration date is 2025-12-01, and its SSL certificate was issued by Google Trust Services / WE1 as scanned on 2026-09-10.
The PhishDestroy internal catalogue lists eoxphy.com, with the earliest observation recorded on 2026-09-09. On 2026-09-18, VirusTotal recorded 15 detections out of 89 scanners. OTX reported 5 pulses on 2026-09-10, and the PageSpeed performance score was measured at 96 on 2026-09-09.
The PhishDestroy listing, OTX, VirusTotal, and the HTTP check were collected on different dates, so each source reflects its own distinct observation period. Comparing these records requires attention to their specific dates, as the SSL scan and OTX check occurred together, while the VirusTotal and HTTP observations were later.
Retain all dated evidence for eoxphy.com, including the PhishDestroy listing, OTX pulse count, VirusTotal detection numbers, and HTTP response, to enable accurate comparisons with future records. When reviewing eoxphy.com, avoid submitting any sensitive information until its current status is assessed using updated evidence.
21 · datasets with records / 10 · not recorded
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.
0 · external source matches
Dynadot Inc · 188.114.96.3 · DNS, TLS and retained responses
Edge-IP reputation is not attributed to this domain.
chuck.ns.cloudflare.comgalilea.ns.cloudflare.comLocation describes the IP network.
021332e58b3dd81fb22a06b80779f7e87a93f21d23b491fcb38ebd47e2140497Saved 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 eoxphy.com · 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 browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: http_other: raw=http_404; http=404; via=http_proxy; server=cloudflare
1 · outbound report records
188.114.96.3.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
Reachable→Unavailable
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
live_content→Unknown
stale_current_evidence
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unknown
probe_inconclusive
16→15
Reachable
15 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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
PD-20260909-B75725 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Recovery steps, reporting contacts and complaint drafts
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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
eoxphy.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
Stored evidence snapshot. Source timestamps appear where available.
VirusTotal detections for eoxphy.com: 15 (2026-09-18 02:07:21 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.