VirusTotal
5 / 89
On 2026-10-01, americanexpress-authentifizierung.com returned an HTTP status code of 502 during an HTTP check. The domain was first observed on 2026-07-28, according to the recorded first-observed timestamp.
The PhishDestroy internal listing records this domain, and the blocklist check was performed on 2026-10-01. OTX recorded two pulses for the domain on 2026-09-13. VirusTotal reported 5 detections out of 89 scanners on 2026-09-13, with observation time unknown. The registrar recorded for the domain is NICENIC INTERNATIONAL GROUP CO., LIMITED.
The HTTP check on 2026-10-01 and the OTX and VirusTotal checks on 2026-09-13 were performed on different dates, so their results describe separate moments rather than a single snapshot. The PhishDestroy internal listing and the OTX pulses are distinct source records, and the first-observed date of 2026-07-28 predates all of these checks. Because the observation dates differ, the HTTP status, detection counts and listing status cannot be treated as simultaneous measurements.
Anyone reviewing americanexpress-authentifizierung.com should retain the dated records from PhishDestroy, OTX, VirusTotal and the HTTP check so later observations can be compared against them. Subsequent checks should be logged with their own dates and source names, allowing changes in status or detection counts to be tracked over time. During any review, avoid submitting sensitive information to the domain until its status is independently confirmed.
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='americanexpress-authentifizierung.com', port=80): Max retries exceeded with url: / (Caused
ollie.ns.cloudflare.comLocation describes the IP network.
9 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