VirusTotal
19 / 91
“auspost.addqwu.com”
auspost.addqwu.com was recorded returning HTTP status 402 on 2026-10-01, according to the most recent HTTP check. This domain was first observed on 2026-09-25 and is included in the PhishDestroy internal listing as of the current evidence set.
The PhishDestroy internal listing shows auspost.addqwu.com as listed, with this status recorded on 2026-10-01. VirusTotal scanned the domain on 2026-09-28, reporting 19 detections out of 91 scanners. The first observation of the domain occurred on 2026-09-25, and the HTTP status 402 was recorded on 2026-10-01.
PhishDestroy, VirusTotal, and the HTTP check each provide records from different dates, which means their observations reflect separate moments in the domain's timeline. The first observation date precedes both the VirusTotal scan and the HTTP status check, so the evidence illustrates how the domain was recorded over time by different sources.
Retain all dated evidence for auspost.addqwu.com, including the PhishDestroy listing, VirusTotal results, and HTTP response, for future comparison. When reviewing subsequent records, compare them to these dated entries and avoid submitting sensitive information to auspost.addqwu.com during the review process.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
workermanScanner note: empty_body: raw=empty_body; http=402; via=http_proxy; server=workerman
ns8.alidns.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
47.79.39.190. 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