VirusTotal
15 / 89
“Überprüfung — La Poste”
The domain meinpostpaket.com returned an HTTP 502 error on 2026-10-01, indicating a server-side failure at that moment. It was first observed on 2026-09-19, showing recent tracking activity.
On 2026-10-01, meinpostpaket.com produced an HTTP 502 response. VirusTotal recorded 15 detections out of 89 scanners on 2026-09-20. OTX listed the domain in three pulses on 2026-09-20. The domain appeared in the PhishDestroy internal listing. Registration was noted with NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-09-17, and a Let's Encrypt / YE1 certificate scan occurred on 2026-09-20.
The HTTP 502 response documents a server error at a specific point in time. VirusTotal and OTX entries reflect security community attention to the domain. The PhishDestroy listing indicates internal review or monitoring activity.
Avoid relying on meinpostpaket.com until its status improves. Keep the HTTP 502 record and VirusTotal, OTX, and PhishDestroy entries for comparison. Watch for updates to these sources to detect any changes.
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='meinpostpaket.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Location describes the IP network.
2c8b59d7e92421ae9f3c216558ccda242800c3f96e964707267d33b888886677Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
45.139.104.212. 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.
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