VirusTotal
16 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“jeremymathew.com”
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.
16 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
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
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.
Stored narrative · generated . Provider checks below retain their own observation dates.
jeremymathew.com returned HTTP status 502 in an HTTP check recorded on 2026-10-01. The domain was first observed on 2026-09-09, and a VirusTotal scan on 2026-09-18 recorded 16 detections across 89 scanners.
The HTTP check on 2026-10-01 recorded status 502, while the domain's first observation was logged on 2026-09-09. VirusTotal, checked on 2026-09-18, reported 16 detections out of 89 scanners. OTX, checked on 2026-09-10, listed 5 pulses, and the PhishDestroy internal catalogue held a listing for the domain. Registration was recorded on 2023-11-20 with registrar NAMECHEAP INC, and the SSL scan on 2026-09-10 named issuer GlobalSign nv-sa / GlobalSign GCC R6 AlphaSSL CA 2025.
The OTX pulses and PhishDestroy listing are separate source records that each associate the domain with reporting, and the VirusTotal detection ratio reflects scanner output on its own checked date. The HTTP 502 response describes only the recorded request outcome, not the domain's full content or current availability. The first observation and the later checks fall on different dates, so the sequence of records can be compared chronologically without treating any single entry as a verdict.
Preserve the HTTP check record for jeremymathew.com and the VirusTotal scan output as separate source documents for later comparison. Retain the OTX pulse record and the PhishDestroy catalogue entry, then compare each against future checks of the same sources. Review the recorded HTTP status alongside the scanner and pulse records before deciding on any blocking or monitoring step.
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.
ns1.greengeeks.netns2.greengeeks.netjeremymathew.compriority 0Location describes the IP network.
05bace928030517d7d17ad6424f237d920ea24afc22da6f27b2cc4ff61f39cbdtrafrobot.ruSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
138.68.122.224.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown
probe_inconclusive
Reachable
10 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.
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