adornmondecollection.shop was observed returning an HTTP 502 error on 2026-10-01, which indicates a recorded server response issue at that time. The domain was also evaluated by VirusTotal and appeared in the PhishDestroy internal catalogue, providing additional perspectives on its status.
Recorded Evidence
On 2026-10-01, adornmondecollection.shop responded with HTTP status 502. VirusTotal checked the domain on 2026-09-20, recording 8 detections out of 89 scanners. The domain was first observed on 2026-09-09 and appeared in the PhishDestroy internal catalogue. OTX pulses were noted on 2026-09-10.
Interpretation
The collected evidence offers a multi-source view of adornmondecollection.shop, including technical response, security scanning, and catalogue listing. The HTTP 502 code documents a specific server issue, while VirusTotal and OTX show how the domain was assessed by external security sources. The PhishDestroy listing adds a record for internal review, and the chronology allows comparison of observations from different dates.
Recommended Actions
For adornmondecollection.shop, retain the HTTP response record and VirusTotal detection results for future reference. Keep OTX pulse information and the PhishDestroy catalogue listing to monitor for updates. Use these source records as benchmarks when reviewing the domain’s technical and security profile.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='adornmondecollection.shop', port=80): Max retries exceeded with url: / (Caused by NewConne
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:31:44 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-24 10:07:30 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-24 10:07:30 UTC → 2026-09-30 16:14:55 UTC · 150.12hmidpoint estimate ≈ 2026-09-27 13:11:12 UTC · precision low · 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 adornmondecollection.shop· checked Sep 9, 2026
71
Needs Work
Performance
FCP
2.75s
First Contentful Paint
LCP
2.75s
Largest Contentful Paint
CLS
0.019
Cumulative Layout Shift
TBT
800ms
Total Blocking Time
SI
4.12s
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-24 22:07:14 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-10 14:46:25 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-10 03:49:00 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-09 14:45:41 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: ネットクラフト.
Threat First Observed2026-09-09 13:09:06 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 80.71.144.122.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
18 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.
