VirusTotal
checked — no detections recorded
The domain merit3.com was referenced in the PhishDestroy internal listing on 2026-10-12, documenting its inclusion in a publisher-specific catalogue. A PageSpeed performance score was also recorded for the domain on the same date, providing additional technical context.
VirusTotal checked merit3.com on 2026-10-12, recording 0 detections out of 92 total scanners. OTX referenced the domain with 2 pulses as of 2026-10-12. The PhishDestroy internal listing included merit3.com on 2026-10-12. A PageSpeed performance score of 82 was recorded for the domain on 2026-10-12.
The PhishDestroy listing contains a record of merit3.com, reflecting its status in the publisher's internal catalogue. VirusTotal documents the domain's scan results, offering a measurement of detections from multiple security vendors. OTX records the domain's presence in its intelligence platform, which tracks domain-related pulses. These sources together provide a snapshot of the domain's technical and security profile as of the recorded dates.
For merit3.com, retain the VirusTotal scan record and the OTX reference for ongoing monitoring and future comparison. Preserve the PhishDestroy internal listing to track any changes in catalogue status. Review the PageSpeed performance score for additional technical assessment in future evaluations.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
Google PageSpeed Insights — mobile performance audit of merit3.com · checked Oct 12, 2026
172.67.223.75. 7 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