Skip to security report
Domain security and threat intelligence
whatsapp.tamil.bid favicon

whatsapp.tamil.bid

“WhatsApp”

Registrar
Dominet (HK)
Resolved IP
64.233.165.121
Registered
Dec 31, 2020
Threat verdict Critical
VirusTotal detections: 17/91 Stored blocklist matches: 1
Oct 6, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 17. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
VirusTotal
17 det.
CF Radar
Malicious
URLScan
URLScan
Age
5.8 yr
PhishDestroy
DestroyList
Listed

Source evidence

5 sources

VirusTotal

17 / 91

Report

CF Radar

provider verdict: malicious

Report

OTX

no community references

Report

URLScan capture

stored report

Report

Google Safe Browsing

Checked; no threat flag recorded

Report
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Evidence Summary

Critical
VirusTotal
17/91
URLScan
Stored capture

Assessment

The domain whatsapp.tamil.bid was listed on the Phishunt blocklist as of 2026-10-06, according to a dated external observation. On the same day, the domain received a PageSpeed performance score of 69, reflecting moderate web performance.

Recorded Evidence

Phishunt included whatsapp.tamil.bid on its blocklist on 2026-10-06. VirusTotal checked the domain on 2026-10-05, reporting 17 detections out of 91 scanners. The domain was first observed on 2026-10-06, and Phishdestroy internally listed it on that date as well.

Interpretation

These records indicate that whatsapp.tamil.bid was noted by multiple sources, including both external and internal listings, within a short period. The VirusTotal scan aggregates input from a wide range of security vendors, while the PageSpeed score provides a snapshot of the domain's web performance at the time of measurement.

Recommended Actions

Review and retain the Phishunt blocklist entry, VirusTotal scan results, and Phishdestroy internal listing for whatsapp.tamil.bid. Compare these records to monitor any future changes in how this domain is recorded by each source.

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No 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.

Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Stored Capture · 1 capture

Page Title
WhatsApp

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 6, 2026
Registrar (base domain) Dominet (HK) HK(HK)
Registration (base domain)tamil.bid · Created Dec 31, 2020
Technical detailsProvenance & timestamps
First DetectedOct 6, 2026
Submitted URLhttp://whatsapp.tamil.bid/
Favicon Hash
ICANN OVERSIGHT Registration: tamil.bid

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain tamil.bid 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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
64.233.165.121
Network ASN
AS15169
Organization
Google LLC
Observed location
Mountain View, US

Nameservers 1

  • ns8.alidns.com

Location describes the IP network.

viewdns.info · 64.233.165.121rapiddns.io

Latest Classified Outcome 2026-10-06 04:51:16 UTC

Primary outcome Unknown reason: Stale Current Evidence 0% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unknown Content: Unknown DNS: Stale Registration: Unknown
RDAP registration Unknown
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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 17 detections
BitDefender
Chong Lua Dao
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
Seclookup
SOCRadar
Sophos
URLQuery
VIPRE
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of whatsapp.tamil.bid · checked Oct 6, 2026

69
Needs Work
Performance
FCP
3.91s
First Contentful Paint
LCP
5.92s
Largest Contentful Paint
CLS
0.002
Cumulative Layout Shift
TBT
87ms
Total Blocking Time
SI
3.91s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-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.
  1. Threat First Observed 2026-10-06 03:47:44 UTC
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 64.233.165.121.

Threat Response Pipeline

Discovery
Analysis
Monitoring

8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
whatsapp.tamil.bid detected and queued for full analysis
Oct 6, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Cloudflare Radar Report
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.
VirusTotal
17/91 recorded on VirusTotal
Oct 6, 2026
Blocklist Detection
Found in 1 blocklist: Phishunt
Oct 6, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing, Phishing, Security threats
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
DestroyList Published
Oct 6, 2026
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
urlscan.ioScreenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotalMulti-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare RadarDNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTXThreat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback MachineHistorical evidence

Compare archived captures and preserve historical context.

crt.shCertificate Transparency

Inspect certificate records and related hostnames.

DNS Security FiltersQuad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-CheckSurface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Public Blocklist Status

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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.

Europol
Find the official reporting channel for your EU country
National police directory
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/whatsapp.tamil.bid"
  title="PhishDestroy threat report for whatsapp.tamil.bid"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>