On 2026-10-07, amlulworld.shop returned an HTTP 301 status code, indicating a recorded redirect response on that date. The domain was also listed in the PhishDestroy internal catalogue as of the same day.
Recorded Evidence
VirusTotal reported 3 detections out of 92 scanners for amlulworld.shop on 2026-10-07. OTX recorded 4 pulses for this domain on 2026-10-07. The observed page title was AMLUL | AMLUL, and the registrar was Dynadot Inc. with a Let's Encrypt / YE1 SSL certificate as of 2026-10-07.
Interpretation
These source records show that amlulworld.shop has been monitored by multiple security platforms and received a redirect response when accessed. The presence of detections on VirusTotal and activity on OTX indicates that the domain has been noted by threat intelligence and analysis services. The inclusion in the PhishDestroy internal listing further reflects its observation status within that catalogue.
Recommended Actions
For further review, retain the VirusTotal, OTX, and PhishDestroy records related to amlulworld.shop. Compare these sources for any changes or new observations over time. Use the recorded evidence to guide continued monitoring and reference in future assessments.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:13:28 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:13:28 UTClast content: 2026-10-11 01:47:33 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.
使用技術 · 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.
Last analyzed First positive detection Previous stored snapshot: 3 detections
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of amlulworld.shop· checked Oct 7, 2026
68
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
8.63s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
149ms
Total Blocking Time
SI
3.21s
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.
VirusTotal Detections Update2026-10-07 03:47:58 UTC
VirusTotal scanner detections updated from 4 to 3. Resolved alerts: Forcepoint ThreatSeeker.
Threat First Observed2026-10-06 22:12:28 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.238.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
11 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.
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.
(US)
