Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
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.
Recorded Evidence
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.
Interpretation
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.
Recommended Actions
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.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明: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
Primary outcomeRegistration hold observedreason: Registrar clientHold95% confidence
AttributionNICENIC INTERNATIONAL GROUP CO., LIMITEDmechanism: Registrar clientHoldsource: Rdap Status Collector
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Registrar clientHold
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 02:45:12 UTC
RDAP registrationRegistrar clientHoldNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientHoldclientTransferProhibitedexpires 2027-07-24 09:21:20 UTCchecked 2026-10-12 03:45:46 UTC
Registrar action markerverified clientHold markerNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765causal link to our report not established
Observed timelinecurrent episode first observed: 2026-09-13 06:05:54 UTCfirst terminal observation: 2026-09-13 06:05:54 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed First positive detection Previous stored snapshot: 2 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
SOCRadar
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-13 04:51:18 UTC
VirusTotal scanner detections updated from 2 to 5. Added scanner alerts: CRDF, Forcepoint ThreatSeeker, SOCRadar.
Domain Status Transition2026-09-12 23:04:53 UTC
Domain state transitioned from alive to dead.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
已捕获威胁
americanexpress-shield.com 已检测到并排入队，待进行全面分析
2026年7月28日
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
2026年10月13日
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
