URLScan verdict
malicious
Report“Tanning Baked | Baked”
bakedtanningshop.shop was recorded with a PhishDestroy internal listing on 2026-10-10, the same date as its first observation. The domain was also observed resolving to an IP address in the US on that date.
PhishDestroy documented an internal listing for bakedtanningshop.shop on 2026-10-10. The SSL certificate issued by Let's Encrypt / YE1 was scanned on 2026-10-10, and the domain’s first observation date is also 2026-10-10.
The PhishDestroy record for bakedtanningshop.shop contains a dated entry measuring its presence in a publisher-maintained catalogue. This source provides a technical reference for the domain’s observation and listing, allowing comparison with other evidence. The SSL certificate scan adds context to the security profile documented on the same date.
Preserve the PhishDestroy internal listing and SSL certificate scan records for bakedtanningshop.shop as reference points. Use these dated entries to compare with any future evidence or additional source records for the domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
CaddyScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://bakedtanningshop.shop/; server=Caddy
macy.ns.cloudflare.comned.ns.cloudflare.comLocation describes the IP network.
b25a247353b5157d1484aa3bf6edd46a9cd8b7552ed695c766d0970a19c551e8Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
195.96.130.245. 8 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