Security engines reporting a detection: 6. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 8 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Evidence Summary
Critical
VirusTotal
6/92
OTX
4 community refs
URLScan
Stored capture
Assessment
On 2026-10-07, amandauprichardcollection.shop returned an HTTP 301 status, indicating a recorded redirect response that date. The domain’s PageSpeed performance score was 82 on the same date, reflecting moderate web performance at the time of measurement.
Recorded Evidence
On 2026-10-07, VirusTotal reported 0 detections out of 92 scanners for amandauprichardcollection.shop. The domain appeared in the PhishDestroy internal listing as of that date. OTX pulses referenced the domain on 2026-10-07. The registrar was Dynadot Inc. and the SSL certificate was issued by Let's Encrypt / YE2 on 2026-10-07.
Interpretation
These dated records show how amandauprichardcollection.shop was observed across multiple monitoring systems on 2026-10-07. The HTTP response, performance score, and inclusion in OTX and PhishDestroy reflect technical and security monitoring activity at that time.
Recommended Actions
Retain the HTTP 301 response and PageSpeed performance score for baseline technical analysis of amandauprichardcollection.shop. Compare the VirusTotal, PhishDestroy, and OTX records over time to track any changes in security observations.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
RegistrationCreated May 20, 2026 (147d)—Expires May 20, 2027
Elapsed Since First Report7 days
What we count
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Last known active.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 6, 2026
DOM Analysisanalyzed Oct 9, 2026score 88/1002 brand signals
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-13 22:07:57 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 22:07:57 UTClast content: 2026-10-13 22:07:57 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.
Technologies · 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: 5 detections
alphaMountain.ai
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Netcraft
SOCRadar
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of amandauprichardcollection.shop· checked Oct 7, 2026
82
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
3.75s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
148ms
Total Blocking Time
SI
2.89s
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-10-13 22:29:37 UTC
Source: PhishDestroy monitoringEvent details
Domain state transitioned from alive to dead.
Threat First Observed2026-10-06 21:56:25 UTC
Source: PhishDestroy monitoringEvent details
Domain ingestion complete. Initial state is marked as alive pointing to IP 212.52.28.53.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
amandauprichardcollection.shop detected and queued for full analysis
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.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
6 evidence signal groups linked1 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches1
Same favicon hash or the same page title as this host.
Report 
(US)
