VirusTotal
1 / 92
“Custom Rings & Men’s Wedding Bands | Aydins Jewelry”
aydinsjewelry.shop was observed with an HTTP status code 200 on 2026-10-09, indicating a responsive server at that time. A PageSpeed performance score of 90 was also recorded, providing a technical benchmark for the domain.
VirusTotal reported 1 detection out of 92 scanners for aydinsjewelry.shop on 2026-10-09. OTX referenced the domain in four pulses as of 2026-10-09. The PhishDestroy internal catalogue included the domain, and the SSL certificate issuer was Let's Encrypt / YE1, both noted on 2026-10-09.
The collected evidence from VirusTotal, OTX, and PhishDestroy offers a multi-source snapshot of aydinsjewelry.shop. These records, combined with technical performance and certificate details, allow for comparison against future observations and provide context for ongoing domain monitoring.
For aydinsjewelry.shop, retain the VirusTotal, OTX, and PhishDestroy records for reference in future reviews. Use the HTTP response and PageSpeed score as technical benchmarks when assessing new data. Compare these source entries to subsequent findings to track any changes in detection or catalogue status.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: alive_content: raw=ok; http=200; via=https_proxy
evan.ns.cloudflare.compaloma.ns.cloudflare.comLocation describes the IP network.
bd214aa614be62db095f008431e0953b7627704b77db28a1f01c761cd515e520Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of aydinsjewelry.shop · checked Oct 9, 2026
195.96.130.203. 10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive