Skip to security report
Analytics Dashboard
Domain security and threat intelligence
whatsapp-indonesia877.blogspot.com favicon

whatsapp-indonesia877.blogspot.com

In short

whatsapp-indonesia877.blogspot.com is a WhatsApp impersonation page detected by PhishDestroy on 2026-09-05. Risk: critical (100/100). Registrar: Google Domains. Status: Last known active. Hosting: GOOGLE - Google LLC, US. VirusTotal: 17/89 engines flag it. Do not enter credentials or connect a wallet.

“WhatsApp”

Registrar
Google Domains
Resolved IP
142.251.13.132
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 17/89 Stored blocklist matches: 2 Automated brand label: WhatsApp
Sep 5, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 17. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
17 / 89
engine detections
Google Safe Browsing
No threat flag
Page captures
9
open gallery
Source evidenceVirusTotal 17 / 89 6 sources

VirusTotal

17 / 89 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
17 / 89
Page captures
9
Page captures Source results Registration record

PhishDestroy threat report

Overview

whatsapp-indonesia877.blogspot.com is a WhatsApp impersonation phishing page hosted as a Blogger blog. Its page title is simply "WhatsApp", and the 'indonesia877' name suggests it targets Indonesian-speaking users. PhishDestroy first flagged it on 2026-09-05. It was still online and serving content when last checked on 2026-10-19.

How the scam works

Pages like this copy WhatsApp's name and look so a visitor believes they are dealing with the real service. These schemes usually ask for a phone number, the six-digit SMS verification code or a two-step PIN under a pretext such as account verification, a prize, or joining a group. Anyone who hands over that code can lose the WhatsApp account to the attacker, who then messages the victim's contacts asking for money or more codes. Such pages may also collect personal details for later fraud.

Evidence

VirusTotal shows 17 of 89 security engines flagging the page as of 2026-09-16, including BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, Criminal IP and CyRadar. That spread of independent vendors makes a false positive unlikely. urlscan.io gave a malicious verdict and identified WhatsApp as the brand being imitated. The page is listed on the PhishDestroy blocklist.

Infrastructure

The site sits on Google's free Blogger platform. It is served from Google's US network and uses a Google Trust Services certificate. The 2000-07-31 registration date and the Google LLC registrar belong to the parent blogspot.com domain, not to this blog, so they say nothing about when the operator set it up. Free Blogger subdomains like this cost nothing to create and inherit Google's reputation and HTTPS padlock, so the padlock is no sign of legitimacy. The operator can also replace the page quickly once it is reported.

What to do

If you entered a WhatsApp verification code or PIN on this page, reinstall or re-register WhatsApp on your phone with your number right away to push the attacker out. Then turn on two-step verification with a new PIN. Warn your contacts not to answer money requests that seem to come from you, and treat any personal details you submitted as exposed. Defenders should block the subdomain and report it to Google's Blogger abuse channel. It is also worth watching for sibling blogspot subdomains that use the same 'whatsapp-indonesia' naming pattern.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-05T15:00:11Z

Observed: · Retrieved:

Uuid
01a07215-67b5-766b-9a76-beda5d6d0ea5
Final url
https://whatsapp-indonesia877.blogspot.com/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://whatsapp-indonesia877.blogspot.com/",
        "from": "http://whatsapp-indonesia877.blogspot.com/",
        "status": 307
    },
    {
        "to": "https://whatsapp-indonesia877.blogspot.com/",
        "from": "https://whatsapp-indonesia877.blogspot.com/",
        "status": 302
    }
]
Ip
172.217.25.161
Ptr
kix06s19-in-f1.1e100.net
Contacted domains
[
    "blogger.googleusercontent.com",
    "www.blogger.com",
    "resources.blogblog.com",
    "pbs.twimg.com",
    "1.bp.blogspot.com",
    "3.bp.blogspot.com",
    "samsatjakarta.wordpress.com",
    "samsatpoldametrojayajkt.wordpress.com"
]
Contacted IP addresses
[
    "151.101.28.159",
    "142.250.195.129",
    "172.217.25.193",
    "142.250.195.137",
    "172.217.25.161"
]
Asns
[
    "54113",
    "15169"
]
Countries
[
    "AU",
    "US"
]
Linked domains
[
    "www.blogger.com",
    "whatsapp-indonesia17.blogspot.com",
    "blogger.googleusercontent.com",
    "tselpoin27.blogspot.co.id",
    "http"
]
Document hash
1d8901f9fe3134e1cef1b655f49545afbb1dd06dfa0075d9e549f61ce1df31db
Globals
[
    "BLOG_attachCsiOnload",
    "_WidgetManager",
    "_WidgetInfo",
    "widget_module_provide",
    "_AdSenseView",
    "_BlogArchiveView",
    "_AttributionView",
    "_BlogView",
    "_BlogListView",
    "_BlogSearchView",
    "_ContactFormView",
    "_ExampleView",
    "_FeaturedPostView",
    "_FeedView",
    "_FollowersView",
    "_HeaderView",
    "_TextView",
    "_HTMLView",
    "_ImageView",
    "_LabelView",
    "_TextListView",
    "_LinkListView",
    "_BloggerButtonView",
    "_NavbarView",
    "_PageListView",
    "_PollView",
    "_PopularPostsView",
    "_ProfileView",
    "_RecentPostsView",
    "_ReportAbuseView",
    "_SharingView",
    "_StatsView",
    "_SubscribeView",
    "_SW_toggleReaderList",
    "_SW_hideReaderList",
    "_TranslateView",
    "_WikipediaView",
    "__wavt",
    "__gjsload__",
    "closure_lm_938711"
]
Tls
{
    "san": [
        "misc-sni.blogspot.com",
        "blogspot.ae",
        "*.blogspot.ae",
        "blogspot.al",
        "*.blogspot.al",
        "blogspot.am",
        "*.blogspot.am",
        "blogspot.ba",
        "*.blogspot.ba",
        "blogspot.be"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR2",
    "subject": "misc-sni.blogspot.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-02T08:38:44Z",
    "valid_from": "2026-08-10T08:38:45Z"
}
Domain age days
1
Apex age days
1
Tls age days
26
Tls valid days
83
Requests
64
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "whatsapp"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "WhatsApp"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "GSE",
    "content-type": "text/html; charset=UTF-8",
    "x-content-type-options": "nosniff"
}
Cloudflare Radar · 2026-09-05T15:39:57Z

Observed: · Retrieved:

Uuid
0ed5ce05-dd28-4975-a16c-34c0c2610627
Final url
https://whatsapp-indonesia877.blogspot.com/
Status
200
History
[
    {
        "url": "https://whatsapp-indonesia877.blogspot.com/",
        "status": 200
    }
]
DOM structure hash
d09a667b64bcf9a8fedc45bf0dac855fd469cf896ae9d037bad36767acd92cd4
Document hash
b71de075b3b48633c1a71284e0f27509d08ef0492a537dfea5cca1b2baaf9ec9
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "1.bp.blogspot.com",
        "type": "CNAME",
        "value": "photos-ugc.l.googleusercontent.com"
    },
    {
        "name": "1.bp.blogspot.com",
        "type": "CNAME",
        "value": "photos-ugc.l.googleusercontent.com"
    },
    {
        "name": "3.bp.blogspot.com",
        "type": "CNAME",
        "value": "photos-ugc.l.googleusercontent.com"
    },
    {
        "name": "3.bp.blogspot.com",
        "type": "CNAME",
        "value": "photos-ugc.l.googleusercontent.com"
    },
    {
        "name": "whatsapp-indonesia877.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "name": "whatsapp-indonesia877.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    }
]
Dnssec valid
false
Ip
142.250.151.132
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2000-07-31T21:38:58Z",
    "updated": "2026-06-29T10:34:06Z",
    "expires": "2027-07-31T21:38:58Z",
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ]
}

Questions about whatsapp-indonesia877.blogspot.com

Is whatsapp-indonesia877.blogspot.com legit?

No. PhishDestroy classifies whatsapp-indonesia877.blogspot.com as a WhatsApp impersonation page (risk: critical, 100/100); it was first detected on 2026-09-05. VirusTotal: 17/89 engines flag it. Treat the site as unsafe.

Is whatsapp-indonesia877.blogspot.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on whatsapp-indonesia877.blogspot.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used whatsapp-indonesia877.blogspot.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesOpenPhish · PhishDestroy · Phishunt 3
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Last checked

Stored Capture · 9 captures

Primary capture 1 / 9
SourcePrimary capture
Recorded2026-09-05 15:02 UTC
StateStored capture
Position1 / 9
Open capture Wayback Download

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Whatsapp report ↗
IP Reputation abuse score 0/100 14 reports Email SpamPort ScanHackingBrute-ForceExploited Host checked Oct 5, 2026
Platform provider Google Domains US(US)
Abuse contactnetwork-abuse@google.com, abuse@google.com
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 5, 2026
DOM Analysisanalyzed Sep 5, 2026score 93/1001 brand signal
Submitted URLhttp://whatsapp-indonesia877.blogspot.com/
Favicon Hash
Observed page title
WhatsApp
Automated brand references
WhatsApp
TLS Certificate
Issued by Google Trust Services · stored validity ends in 55 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
142.251.13.132
Network ASN
AS15169
Organization
GOOGLE - Google LLC, US
Observed location
US
Server header
GSE

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-08-10 08:38:53
Valid until
2026-11-02 08:38:52
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-05 16:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte5d9849ee7b4356add4a6fa767fbe571b3ef8fe1fae66e6b173d889bfe84e27f
Certificate names · 70 SANs
  • blogspot.ae
  • blogspot.al
  • blogspot.am
  • blogspot.ba
  • blogspot.be
  • blogspot.bg
  • blogspot.ca
  • blogspot.ch
  • blogspot.cl
  • blogspot.co.at
  • blogspot.co.id
  • blogspot.co.il
  • blogspot.co.ke
  • blogspot.co.nz
  • blogspot.co.uk
  • blogspot.co.za
  • blogspot.com
  • blogspot.com.ar
  • blogspot.com.au
  • blogspot.com.br
  • blogspot.com.by
  • blogspot.com.co
  • blogspot.com.cy
  • blogspot.com.ee
  • blogspot.com.eg
  • blogspot.com.es
  • blogspot.com.mt
  • blogspot.com.ng
  • blogspot.com.tr
  • blogspot.com.uy
  • blogspot.cz
  • blogspot.de
  • blogspot.dk
  • blogspot.fi
  • blogspot.fr
  • blogspot.gr
  • blogspot.hk
  • blogspot.hr
  • blogspot.hu
  • blogspot.ie
  • blogspot.in
  • blogspot.is
  • blogspot.it
  • blogspot.jp
  • blogspot.kr
  • blogspot.li
  • blogspot.lt
  • blogspot.lu
  • blogspot.md
  • blogspot.mk
  • blogspot.mx
  • blogspot.my
  • blogspot.nl
  • blogspot.no
  • blogspot.pe
  • blogspot.pt
  • blogspot.qa
  • blogspot.ro
  • blogspot.rs
  • blogspot.ru
  • blogspot.se
  • blogspot.sg
  • blogspot.si
  • blogspot.sk
  • blogspot.sn
  • blogspot.tw
  • blogspot.ug
  • blogspot.vn
  • bp.blogspot.com
  • misc-sni.blogspot.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 142.251.13.132rapiddns.io

Latest Classified Outcome 2026-10-21 22:14:45 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-21 22:14:45 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-21 22:14:45 UTC last content: 2026-10-21 22:14:45 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 · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 17 detections
Criminal IP
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of whatsapp-indonesia877.blogspot.com · checked Sep 5, 2026

67
Needs Work
Performance
FCP
3.43s
First Contentful Paint
LCP
35.66s
Largest Contentful Paint
CLS
0.01
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.86s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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.

whatsapp-indonesia877.blogspot.com
Saved result
Unreachable
Stored observation history22

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 17
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. VirusTotal · Detection count

    14→17

  14. VirusTotal · Detection count

    13→14

  15. VirusTotal · Detection count

    12→13

  16. VirusTotal · Detection count

    8→12

  17. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    17/89 engine detections

    View source
  3. Added to PhishDestroy

    whatsapp-indonesia877.blogspot.com

    View source
  4. URLScan

    Page captured

    View source

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 17 det. ChainPatrol URLQuery Scamadviser 80 trust SSL Labs Certificate hostname mismatch CF Radar Malicious WOT Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including whatsapp-indonesia877.blogspot.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/whatsapp-indonesia877.blogspot.com"
  title="PhishDestroy threat report for whatsapp-indonesia877.blogspot.com"
  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>