VirusTotal
13 / 91
“FASTPANEL”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse-contact@publicdomainregistry.com.
The latest stored availability evidence still shows the domain reachable; 23 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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | lenticularhost.net |
malicious | Sinkholed |
| Cloudflare DNS | lenticularhost.net |
malicious | Sinkholed |
| DNS4EU | lenticularhost.net |
malicious | Sinkholed |
| Quad9 DNS | lenticularhost.net |
malicious | Sinkholed |
On 2026-10-01, lenticularhost.net returned an HTTP status code 200, indicating a recorded response on that date. The domain was also listed in the PhishDestroy internal catalogue as of the same period.
An HTTP check on 2026-10-01 recorded a 200 status for lenticularhost.net. VirusTotal, checked on 2026-09-29, reported 13 detections out of 91 scanners. OTX, checked on 2026-09-18, listed 4 pulses for this domain. The domain was registered on 2023-11-16 with PDR Ltd. d/b/a PublicDomainRegistry.com, and its SSL certificate, scanned on 2026-09-15, was issued by FASTPANEL / parking.
The OTX pulse record, PhishDestroy internal listing, and VirusTotal detections each represent separate source observations, each with its own check date. The HTTP 200 status documents a response at a specific time but does not describe the content or purpose of the domain. These records allow for comparison across different types of source data without combining them into a single assessment.
Retain the PhishDestroy internal listing and OTX pulse records for lenticularhost.net for future reference and comparison. Keep the VirusTotal detection record with its scanner count as a baseline for subsequent checks. Preserve the HTTP response record to compare with later observations. Schedule regular reviews of these sources and document each result with its date for ongoing monitoring.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginx/1.30.0Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.30.0
ns1.mysecurecloudhost.comns2.mysecurecloudhost.comns3.mysecurecloudhost.comns4.mysecurecloudhost.comlenticularhost.netpriority 0Location describes the IP network.
e7a3414bb08205342e6d68b5bc79b1a57cb09b37772f5447fcf2c968aee9bf39Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
154.83.186.200. 12 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-20260915-2E1D03 Recipient: abuse-contact@publicdomainregistry.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 (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. 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