VirusTotal
5 / 89
On 2026-10-01, americanexpress-shield.com returned an HTTP 502 status code, indicating a recorded server error at that time. The domain was also observed to have internal listing in the PhishDestroy catalogue.
VirusTotal checked americanexpress-shield.com on 2026-09-13, recording 5 detections out of 89 scanners. OTX pulses were noted on 2026-09-13, and the domain was first observed on 2026-07-28. The registrar is NICENIC INTERNATIONAL GROUP CO., LIMITED.
The available records from VirusTotal, OTX, and PhishDestroy provide a multi-source view of americanexpress-shield.com’s observed status. These dated observations highlight both technical and catalogue-based findings, allowing for comparison across different security platforms. Each source offers a distinct perspective on the domain’s history and recorded events.
For americanexpress-shield.com, retain the HTTP response records and VirusTotal detection results for ongoing review. Compare the OTX pulse history and PhishDestroy internal listing to monitor any future changes or updates. Use these sources to inform further investigation or response actions as needed.
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-shield.com', port=80): Max retries exceeded with url: / (Caused by NewConn
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