VirusTotal
2 / 92 engine detections
Open report2 / 92 engine detections
Open reportDBL_PHISH
2 community references
Open reportScan report
Open reportNo threat flag
Open reportPage capture
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has classified insurancewave.in as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-20; no page title or content was captured at that time.
The current evidence does not tie the domain to a specific phishing or fraud scheme. Its inclusion on phishing blocklists and minor VirusTotal detections suggests it may be used for deceptive purposes, but no concrete mechanism has been observed.
VirusTotal reported 2 detections from 92 scanning engines on 2026-10-20, with alphaMountain.ai and Fortinet flagging the site. Google Safe Browsing showed no warning as of the same date. The domain appears on OpenPhish, Spamhaus DBL (category phishing), has two OTX pulses, and PhishDestroy’s internal list also marks it.
The domain was registered on 2026-02-09 through Hostinger operations, UAB. Hosting records show the site resolved to IP 91.204.209.6, belonging to Enix Ltd in GB.
Visitors should avoid entering any credentials or personal data on the site and treat any communications from it as untrusted. Organizations should block outbound connections to insurancewave.in and monitor logs for any past requests to the recorded IP. If credentials were submitted, change them immediately and review associated accounts for unauthorized activity.
Last checked
ns1.teqzero.comns2.teqzero.comLocation describes the IP network.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
autoconfig.insurancewave.inDomain recordautodiscover.insurancewave.inDomain recordcpanel.insurancewave.inDomain recordcpcalendars.insurancewave.inDomain recordcpcontacts.insurancewave.inDomain recordmail.insurancewave.inDomain recordwebdisk.insurancewave.inDomain recordwebmail.insurancewave.inDomain recordwww.insurancewave.inDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of insurancewave.in · checked Oct 20, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://insurancewave.in/wp-includes/acrobat.htmlContent-Type: text/htmlContent-Encoding: gzipServer: LiteSpeedbytesKeep-Alivegzip15562text/htmlTue, 20 Oct 2026 14:25:13 GMTtimeout=5, max=100Wed, 07 Oct 2026 23:47:09 GMTLiteSpeedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
2 community references
View sourceNo threat flag
View source2/92 engine detections
View sourceinsurancewave.in
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
insurancewave.in
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
insurancewave.in)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
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.