VirusTotal
5 / 89
“404 Not Found”
On 2026-10-01, itauktioner.se returned HTTP status 404 in the recorded HTTP check, indicating the requested resource was not found at that time. Separately, the domain was first observed on 2026-08-31, and a PhishDestroy internal listing was recorded for it.
The HTTP check on 2026-10-01 recorded status 404 for itauktioner.se. A PhishDestroy internal listing was recorded for the domain, and the OTX check on 2026-09-10 returned 4 pulses. VirusTotal, checked on 2026-09-14, reported 5 detections across 89 scanners. The SSL scan on 2026-09-12 identified the issuer as Let's Encrypt / YR2, and the IP address 46.30.211.38 was recorded with country DK and organization Webcluster services.
These records describe separate observations made by different sources on different dates, so they should be read as distinct data points rather than a single combined measurement. The OTX pulses and VirusTotal detections come from independent checks, and neither source's count should be merged with the other to form a conclusion. The 404 response reflects only the recorded HTTP request on its date, not the domain's content or availability at other times.
For itauktioner.se, preserve the PhishDestroy listing record and the OTX pulse record as separate items for later comparison. Also retain the VirusTotal detection record and the HTTP check record, keeping each source's own values intact. Compare these preserved records against future observations of the same sources rather than against one another.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginx/1.18.0 (Ubuntu)Scanner note: alive_content: raw=ok; http=200; via=http_proxy; server=nginx/1.18.0 (Ubuntu)
ns02.one.comLocation describes the IP network.
5aad284109edc72bbaa3e7e8ff69b601d0d170543aa3ed49fb526f2216318c5bone.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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