Skip to security report
Domain security and threat intelligence
hadiah-resmi1577.blogspot.com favicon

hadiah-resmi1577.blogspot.com

In short

hadiah-resmi1577.blogspot.com is a Shopee impersonation page detected by PhishDestroy on 2026-08-31. Risk: critical (100/100). Registrar: Google Domains. Status: Last known active. Hosting: Google LLC. VirusTotal: 16/89 engines flag it. Do not enter credentials or connect a wallet.

“Shopee”

Registrar
Google Domains
Resolved IP
142.251.13.132
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 16/89 Automated brand label: Shopee
Aug 31, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Source evidenceVirusTotal 16 / 89 5 sources

VirusTotal

16 / 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

Analysis

Critical
VirusTotal
16 / 89
Page captures
2

PhishDestroy threat report

Overview

hadiah-resmi1577.blogspot.com is an impersonation phishing page posing as Shopee. Its page title reads simply "Shopee", and the subdomain name means roughly "official prize" in Indonesian, which points to a giveaway lure aimed at Shopee's Southeast Asian shoppers. PhishDestroy first flagged it on 2026-08-31. The page was still online and serving content on 2026-10-19.

How the scam works

Fake Shopee prize pages tell visitors they have won a reward, voucher or lucky draw and must "claim" it. The claim process walks the victim through forms that ask for the phone number or email tied to their Shopee account, the password, the one-time code Shopee sends by SMS, and sometimes a ShopeePay PIN or bank card details. With those, the operator can take over the account, spend the wallet balance or linked payment methods, and reuse the identity for further fraud. Some versions also demand a small "admin" or "delivery" fee before the prize is released, and the prize never arrives.

Evidence

On 2026-09-12, 16 of 89 VirusTotal engines flagged the page, including BitDefender, ESET, Fortinet, Emsisoft, Forcepoint ThreatSeeker, alphaMountain.ai, CyRadar and the Vietnamese anti-scam project Chong Lua Dao. That is a solid minority of engines from unrelated vendors reaching the same conclusion. urlscan.io independently rated the page malicious and recognised the Shopee branding on it. The domain is listed on the PhishDestroy blocklist.

Infrastructure

The site is a free Blogger blog, so the 2000-07-31 registration date and the Google LLC registrar belong to the parent blogspot.com platform, not to the scammer. Hosting runs on Google's network in the US, and the TLS certificate from Google Trust Services is the platform default. The padlock shows only that the connection is encrypted. It says nothing about whether Shopee is behind the page. Disposable Blogspot subdomains with numbered names like this one cost nothing to create and are easy to replace once one is reported.

What to do

If you entered details on this page, change your Shopee password at once through the official app, sign out other sessions, and check your linked email and phone number for changes. Contact Shopee support and your bank if you shared a ShopeePay PIN, card number or SMS code, and watch for unfamiliar orders or wallet transfers. Shopee never asks for OTP codes to release a prize, so treat any request like that as fraud. Defenders should block this hostname and report it through Blogger's abuse channel and to Shopee's brand protection team.

Collected source details

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

URLScan · 2026-08-31T07:53:44Z

Observed: · Retrieved:

Uuid
01a056cf-25ac-75fa-960c-3b990efb5ce1
Final url
https://hadiah-resmi1577.blogspot.com/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://hadiah-resmi1577.blogspot.com/",
        "from": "http://hadiah-resmi1577.blogspot.com/",
        "status": 307
    },
    {
        "to": "https://hadiah-resmi1577.blogspot.com/",
        "from": "https://hadiah-resmi1577.blogspot.com/",
        "status": 302
    }
]
Ip
142.250.195.97
Ptr
tzsyda-ad-in-f1.1e100.net
Contacted domains
[
    "blogger.googleusercontent.com",
    "www.blogger.com",
    "resources.blogblog.com",
    "4.bp.blogspot.com"
]
Contacted IP addresses
[
    "172.217.25.161",
    "142.250.195.129",
    "142.251.222.9",
    "142.250.195.169",
    "142.250.195.97"
]
Asns
[
    "15169"
]
Countries
[
    "US"
]
Linked domains
[
    "www.blogger.com",
    "blogger.googleusercontent.com",
    "api.whatsapp.com"
]
Social
[
    "https://api.whatsapp.com/send"
]
Document hash
8f9d1a2bb90a9b5969806e3a8096a6fa447e9e818a2a2e825de9a2afb69c6f60
Globals
[
    "ontouchcancel",
    "ontouchend",
    "ontouchmove",
    "ontouchstart",
    "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"
]
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
28
Apex age days
28
Tls age days
20
Tls valid days
83
Requests
62
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "shopee"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Shopee"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "GSE",
    "content-type": "text/html; charset=UTF-8",
    "x-content-type-options": "nosniff"
}
Cloudflare Radar · 2026-08-31T08:32:16Z

Observed: · Retrieved:

Uuid
a50ba537-d8b8-4ee8-a0ab-5d8693e9fdbb
Final url
https://hadiah-resmi1577.blogspot.com/
Status
200
Redirected
https-only
History
[
    {
        "url": "http://hadiah-resmi1577.blogspot.com/",
        "status": 307
    },
    {
        "url": "https://hadiah-resmi1577.blogspot.com/",
        "status": 200
    }
]
DOM structure hash
93f7307316acbd22f13ea06ab5a3e73e5e3e55fbc15f83bc4a49fe20c15e0468
Document hash
53eba6c958a561c1416ed025b25ffa64832060ac8e364d0f078d7a982db19597
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "4.bp.blogspot.com",
        "type": "CNAME",
        "value": "photos-ugc.l.googleusercontent.com"
    },
    {
        "name": "4.bp.blogspot.com",
        "type": "CNAME",
        "value": "photos-ugc.l.googleusercontent.com"
    },
    {
        "name": "hadiah-resmi1577.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "name": "hadiah-resmi1577.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    }
]
Dnssec valid
false
Ip
172.217.17.193
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 hadiah-resmi1577.blogspot.com

Is hadiah-resmi1577.blogspot.com legit?

No. PhishDestroy classifies hadiah-resmi1577.blogspot.com as a Shopee impersonation page (risk: critical, 100/100); it was first detected on 2026-08-31. VirusTotal: 16/89 engines flag it. Treat the site as unsafe.

Is hadiah-resmi1577.blogspot.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on hadiah-resmi1577.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 hadiah-resmi1577.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 matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 2 captures

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Shopee report ↗
IP Reputation abuse score 0/100 12 reports Port ScanHackingBrute-ForceExploited Host checked Sep 30, 2026
Platform provider Google Domains US(US)
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedAug 31, 2026
DOM Analysisanalyzed Oct 9, 2026score 93/1001 brand signal
Submitted URLhttp://hadiah-resmi1577.blogspot.com/
Favicon Hash
Observed page title
Shopee
Automated brand references
WhatsApp
TLS Certificate
Issued by Google Trust Services · stored validity ends in 61 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
142.251.13.132
Network ASN
AS15169
Organization
Google LLC
Observed location
Mountain View, 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-08-31 10:02:04 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.

Latest Classified Outcome 2026-10-22 10:11:00 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-22 10:11:00 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:11:00 UTC last content: 2026-10-22 10:11:00 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

16 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
MalwareURL
Netcraft
Sophos
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 hadiah-resmi1577.blogspot.com · checked Aug 31, 2026

72
Needs Work
Performance
FCP
1.83s
First Contentful Paint
LCP
13.35s
Largest Contentful Paint
CLS
0.079
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.83s
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.

Stored observation history19

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

    18→16

  14. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    16/89 engine detections

    View source
  3. Added to PhishDestroy

    hadiah-resmi1577.blogspot.com

    View source
  4. URLScan

    Page captured

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

hadiah-resmi1577.blogspot.com

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

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

Official reporting routes

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

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.

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/hadiah-resmi1577.blogspot.com"
  title="PhishDestroy threat report for hadiah-resmi1577.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>