alligatorwarehousestore.shop returned an HTTP 502 status on 2026-10-01, a recorded server response captured during an HTTP check. The domain was first observed on 2026-09-26, and the PhishDestroy internal listing records it in that publisher-owned catalogue.
Recorded Evidence
The HTTP check on 2026-10-01 recorded a 502 response. VirusTotal, checked on 2026-09-29, reported 8 detections out of 91 scanners. OTX, checked on 2026-09-29, showed 4 pulses. The SSL scan on 2026-09-26 identified Let's Encrypt / YE2 as the certificate issuer. The PageSpeed check on 2026-09-26 recorded a performance score of 72.
Interpretation
The HTTP, VirusTotal, OTX, SSL and PageSpeed records each describe a different measurement of alligatorwarehousestore.shop, so no single source captures the whole picture. The VirusTotal and OTX checks share a calendar date, yet a shared date does not make their counts directly comparable. The earlier SSL and PageSpeed observations predate the HTTP check, but different dates alone do not demonstrate a change.
Recommended Actions
For alligatorwarehousestore.shop, preserve the PhishDestroy internal listing and the HTTP status record for later comparison. Compare the VirusTotal and OTX records as separate sources rather than merging their values. Retain the SSL and PageSpeed observations as technical reference points. Schedule fresh checks to compare against these recorded observations.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='alligatorwarehousestore.shop', port=80): Max retries exceeded with url: / (Caused by NewCo
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:32:38 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-29 01:40:37 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-29 01:40:37 UTC → 2026-09-30 16:14:55 UTC · 38.57hmidpoint estimate ≈ 2026-09-29 20:57:46 UTC · precision medium · basis bounded
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.
技术 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Google PageSpeed Insights — mobile performance audit of alligatorwarehousestore.shop· checked Sep 26, 2026
72
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
2.86s
Largest Contentful Paint
CLS
0.009
Cumulative Layout Shift
TBT
756ms
Total Blocking Time
SI
2.86s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Domain Status Transition2026-09-29 22:08:45 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-27 15:07:48 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 19:51:20 UTC
VirusTotal scanner detections updated from 8 to 7. Resolved alerts: Fortinet.
Threat First Observed2026-09-26 15:43:20 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.245.239.137.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
17 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
