app.web3cryptosecure.online poses a credential theft risk by impersonating a Web3 crypto security service to steal login credentials from unsuspecting users. Threat actors registered this domain on January 20, 2026, through Porkbun LLC and hosted it on IP address 188.114.96.3. The site uses a Let's Encrypt SSL certificate, which may give it an air of legitimacy to trick visitors into entering sensitive information. PhishDestroy identified this domain as active and currently under investigation for clear red flags in its infrastructure and purpose. This domain was flagged by PhishDestroy after analysis revealed it operates with no detections across 95 VirusTotal scan engines, suggesting it remains under the radar for automated detection systems. Its recent creation date, January 20, 2026, is unusually current for a phishing site, which is a common tactic used by cybercriminals to evade established blacklists. Additionally, the use of Let's Encrypt for SSL certificates is often exploited by threat actors to appear trustworthy. The domain’s registrar, Porkbun LLC, has been linked to multiple phishing campaigns, further raising suspicion about its legitimacy. The combination of these factors indicates a high likelihood that this site is designed to harvest user credentials under false pretenses. If you visited app.web3cryptosecure.online, immediately change any passwords you may have entered and enable multi-factor authentication on all associated accounts. Review your devices for malware or unauthorized access and consider using a password manager to detect credential reuse attempts. Report the domain to your cybersecurity team or local authorities if you entered sensitive information. Avoid interacting with this site and warn others who may have encountered it. Always verify the authenticity of websites—especially those requesting login credentials—by checking for mismatched URLs, suspicious domain ages, or unusual SSL certificates.
For the registrable domain web3cryptosecure.online behind this subdomain, 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.
Certificate fingerprint133735dbc2a7d8b2eb5f5dfbf8c2ed945bc05abe70b6eca75dc8d4dd47da4f38Certificate names · 1 SANs
web3cryptosecure.online
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:07:56 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-04-17 23:00:08 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-17 23:00:08 UTC → 2026-09-30 16:14:55 UTC · 3,977.25hmidpoint estimate ≈ 2026-07-09 19:37:31 UTC · precision very low · basis bounded
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.
Google PageSpeed Insights — mobile performance audit of app.web3cryptosecure.online· checked Apr 6, 2026
48
Poor
Performance
FCP
10.59s
First Contentful Paint
LCP
12.4s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
352ms
Total Blocking Time
SI
10.59s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
3977.25
Estimate basis
Bounded by observations
Estimate precision
very_low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='app.web3cryptosecure.online', port=80): Max retries exceeded with url: / (Caused by NewCon
app.web3cryptosecure.online
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(US)
