Security engines reporting a detection: 3. 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@shinjiru.com.my.
The latest stored availability evidence still shows the domain reachable; 14 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.
pepecards.net appears in the PhishDestroy internal listing, recorded as true on 2026-10-01, the date of the blocklist check. Separately, PageSpeed recorded a performance score of 69 for the domain on 2026-09-27.
Recorded Evidence
On 2026-09-27, VirusTotal recorded 1 detection across 91 scanners for pepecards.net. OTX recorded 4 pulses for the domain on 2026-10-01. The PhishDestroy internal listing was recorded as true on 2026-10-01. The registration date was 2025-12-03 with GoDaddy.com, LLC, and the SSL certificate issued by Let's Encrypt / YR1 was scanned on 2026-09-28.
Interpretation
The PhishDestroy listing, VirusTotal detections, and OTX pulses each describe a different kind of source observation, so their values should be read separately rather than combined. The PageSpeed score describes a measured performance aspect recorded on its own date. Because the records carry different dates, a reader can compare them chronologically, but the dates alone do not show a change in the domain.
Recommended Actions
Preserve the VirusTotal, OTX, and PhishDestroy records for pepecards.net so later checks can be compared against them. Keep the PageSpeed performance measurement alongside those records for reference. Re-check pepecards.net against these same sources to see whether new observations appear.
Detection-evasion analysis
Cloaking suspected: scanner and visitor titles differ
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.
Certificate hostname mismatch·
Issued by Let's Encrypt / YR1· stored validity ends in 41 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
101.99.76.53
Network ASN
AS45839
Organization
Shinjiru Technology Sdn Bhd
Observed location
Kuala Lumpur, MY
Server header
nginx
Edge-IP reputation is not attributed to this domain.
Nameservers 2
ns01.domaincontrol.com
ns02.domaincontrol.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR1
Valid from
2026-08-24 20:16:43
Valid until
2026-11-22 20:16:42
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-27 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta2f7be672019f6948a7b1cff32b0f13ffa9d650d22724fac48118bdb1af21048Certificate names · 1 SANs
www.pepecards.net
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-11 22:00:38 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-11 22:00:38 UTClast content: 2026-10-11 22:00:38 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 · 2 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Google PageSpeed Insights — mobile performance audit of pepecards.net· checked Sep 27, 2026
69
Needs Work
Performance
FCP
3.01s
First Contentful Paint
LCP
13.88s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.01s
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-11 01:33:34 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-10-06 22:14:33 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-27 23:16:43 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-27 19:09:23 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 101.99.76.53.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
pepecards.net 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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
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.
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · pepecards.net
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.
Same registrar: GoDaddy6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
