VirusTotal
4 / 89
ReportInterpretation & limits
Engine 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.
4 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
A 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.
Stored narrative · generated . Provider checks below retain their own observation dates.
mail.metaplannet.com returned HTTP status 302 in a check recorded on 2026-10-02, the most recent HTTP observation in this evidence set. The same record set shows the domain first observed on 2026-08-10, roughly seven weeks earlier.
The domain was first observed on 2026-08-10. An HTTP check on 2026-10-02 recorded status 302. A VirusTotal scan on 2026-09-19 reported 4 detections across 89 scanners. An SSL scan on 2026-09-19 identified the issuer as Let's Encrypt / YE1. The domain appears in the publisher-owned PhishDestroy catalogue, and a blocklist check was recorded on 2026-10-02. The resolved IP address was 46.8.8.222, listed in CZ under Gransy s.r.o.
The HTTP 302 response describes only the redirect recorded on that date, not the content served at the destination. The VirusTotal figure reflects scanner output on 2026-09-19 and does not by itself establish intent or outcome. The PhishDestroy listing is a publisher-owned catalogue entry, and its presence should be read alongside the other dated observations rather than as a standalone conclusion. The gap between the first observation and the later checks allows a reader to compare timestamps, but the differing dates do not demonstrate a change in behavior.
Analysts should preserve the PhishDestroy catalogue entry and the VirusTotal scan record for mail.metaplannet.com as separate source artifacts. Compare the HTTP check record against the earlier first-observation entry to see whether the recorded status is consistent over time. Retain the SSL scan record alongside these sources so future reviews can reference the same dated observations. Re-check the domain's HTTP response and catalogue status periodically to refresh the evidence set.
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=SOCKSHTTPConnectionPool(host='mail.metaplannet.com', port=80): Max retries exceeded with url: / (Caused by NewConnection
ns4.ultahost.commail.parktons.compriority 10Location describes the IP network.
4e3e96db82ca747d867ce078f313426c07b407540f443edcf40007de7b708995metaplannet.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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