VirusTotal
5 / 91
“Pepecards | Pepe Card | Pepecard | Pepecards Store | Pepeshop | Pepe CC Shop”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hetzner.com.
The latest stored availability evidence still shows the domain reachable; 24 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.
On 2026-10-01 pepecc.shop returned an HTTP 302 status, a recorded response that describes only that request and not all content on the domain. The same domain carried a Pagespeed performance score of 65 from a 2026-09-19 measurement, a separate observation from a different source.
The domain was listed in the publisher-owned PhishDestroy internal catalogue, and OTX recorded four pulses on 2026-09-21. VirusTotal recorded 4 detections out of 91 scanners on 2026-10-01. The SSL certificate from Let's Encrypt / YR2 was scanned on 2026-09-20, and the earliest observation of pepecc.shop in this record is 2026-09-19.
The PhishDestroy listing and the OTX pulses are catalogue and intelligence entries whose scope is limited to what each source recorded. The VirusTotal detections and the Pagespeed score measure different things, so they cannot be combined into a single verdict or trend. The dates run from 2026-09-19 to 2026-10-01, and because the sources were checked on different days, a shared date would not by itself establish simultaneous measurement.
Preserve the PhishDestroy internal listing and the OTX pulse record for pepecc.shop as separate source records, and compare them against future checks of the same sources. Retain the VirusTotal scan result and the Pagespeed measurement as distinct records, since each covers a different aspect of the domain. Recheck pepecc.shop periodically and compare each new observation with the corresponding earlier source record rather than across sources.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
openrestyScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=openresty
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.
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.
ns1.dnspark.inns2.dnspark.inpepecc.shoppriority 0Location describes the IP network.
7a1e1ac0ef09a11a52a62d71e79fed0a9d3ff253e32aab816523d294ff8ffe4eSaved 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 pepecc.shop · checked Sep 19, 2026
37.27.60.109. 14 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.
PD-20260919-E4BD90 Recipient: abuse@hetzner.com 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.
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