Skip to security report
ivana-alawijosjis.blogspot.com favicon
Domain security and threat intelligence

ivana-alawijosjis.blogspot.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded ivana-alawijosjis.blogspot.com on 2026-11-22. Stored VirusTotal result: 8/92 engines flagged. Analysis time (as stored): 2026-11-21 18:07 UTC. Retrieved (as stored): 2026-11-22 15:29 UTC. Listed by external blocklists: OpenPhish.

Page title: “Ivana Alawi Espesyal sa Facebook”

More about the sources
Recorded security signals

Stored VirusTotal result: 8/92 engines flagged. Analysis time (as stored): 2026-11-21 18:07 UTC. Retrieved (as stored): 2026-11-22 15:29 UTC. Listed by external blocklists: OpenPhish. Use caution — do not enter credentials or personal information.

VirusTotal detections: 8/92 Stored blocklist matches: 1
Registrar
United StatesGoogle Domains
Resolved IP
142.251.127.132
First seen by PhishDestroy
2026-11-22
Page captures
open gallery
2026-11-22

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded ivana-alawijosjis.blogspot.com on 2026-11-22. Stored VirusTotal result: 8/92 engines flagged. Analysis time (as stored): 2026-11-21 18:07 UTC. Retrieved (as stored): 2026-11-22 15:29 UTC. Listed by external blocklists: OpenPhish. Risk: critical (evidence score 84/100). Registrar: Google Domains. Status: Last known active. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
8 / 92
Blocklist matches
1 external + PhishDestroy list
Hosting
142.251.127.132
Registrar
United StatesGoogle Domains
Page captures
3

Recorded source summary

ivana-alawijosjis.blogspot.com is a tenant hostname on Google LLC, not a separately registered domain. PhishDestroy first observed the hostname on Nov 22, 2026. Stored content metadata identifies Facebook as the apparent target. The captured page title is “Ivana Alawi Espesyal sa Facebook”. Current evidence score: 84/100 (critical).

Positive findings are stored from 3 sources: VirusTotal, OpenPhish, and URLScan. VirusTotal recorded 8 detections among 92 engines: ESET, G-Data, Sophos, Fortinet, SOCRadar, LevelBlue, OpenPhish, BitDefender on Nov 21, 2026 at 18:07 UTC. OpenPhish listed the hostname in the separate external-blocklist snapshot on Nov 22, 2026 at 15:20 UTC. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to facebook and assigned phishing as its category on Nov 22, 2026 at 15:26 UTC.

HTTP 200 was recorded on Nov 22, 2026 at 15:27 UTC. Google LLC is the hosting platform for this tenant, not its registrar. At collection time, the hostname resolved to 142.251.127.132. The IP and ASN identify shared Google LLC infrastructure, not the tenant operator. The stored server header is GSE. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and Cloudflare Radar. The platform TLS certificate was issued by Google Trust Services / WE2 with validity through Jan 26, 2027.

The content indicators and 3 positive source findings support the current Facebook impersonation and phishing classification. The target field identifies Facebook.

Source evidenceVirusTotal 8 / 92 3 sources

VirusTotal

8 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
8
Denominator
92
Vendors
BitDefender, ESET, Fortinet, G-Data, LevelBlue, OpenPhish, SOCRadar, Sophos
Observed at
2026-11-21 18:07:44
Checked at
2026-11-22 16:29:36
Fetched at
2026-11-22 15:29:36

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 25 fields

Mail configuration

SPF lookups
0

CAA records

Count
1
Domain
blogspot.com
Allowed issuers
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Crawler rules

Allow
  • /
User agents
  • Mediapartners-Google
  • *
Present
Yes
Disallow
  • /search
  • /share-widget
Sitemap URLs
  • https://ivana-alawijosjis.blogspot.com/sitemap.xml

Sitemap

Urls
  • https://ivana-alawijosjis.blogspot.com/2026/11/done.html
Present
Yes
URL count
1
Lastmod max
Lastmod min

Page title and metadata

Page title
Ivana Alawi Espesyal sa Facebook
Indexing directives
noindex, nofollow
Open Graph image
https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEggkRlJWASHbxL2DY2y94v85lwPNkAsTzVhVjPqS6HNUuQa_iWXzZxupuBYDcSRD7zMRBPXlWUbTIng7cU69_7cVPIO0RdpexEPW7VbFsYJVrNuSw_4QEh9b9fNYEG5kRTXxK86fbZ8T0GZOyFXd_FDbUJ1cq6I14qE1JPsBRCc68yf7FO_S8zws1jbY639/s722/Screenshot_110.png

Trackers

Requests
29
Observed services
  • Name
    Bootstrap CDN
    Company
    BootstrapCDN
    Country
    US
    Category
    Hosting
    Requests
    3
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    3
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google User Content
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    20
  • Name
    blogspot.com
    Company
    Google
    Country
    US
    Category
    Misc
    Requests
    1
  • Name
    Google+ Platform
    Company
    Google
    Country
    US
    Category
    Social Media
    Requests
    2

Forms and mixed content

Scripts without SRI
  • https://apis.google.com/js/platform.js
  • https://apis.google.com/js/plusone.js
  • https://ajax.googleapis.com/ajax/libs/jquery/1.12.1/jquery.min.js
  • https://cdnjs.cloudflare.com/ajax/libs/modernizr/2.7.1/modernizr.min.js
Third-party scripts
5

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
242
Download
0
Response time, ms
280

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
33654
CO₂, grams
0.0012
Cleaner than, %
46

DNS servers

Nameservers
  • IP address
    216.239.32.10
    Host
    ns1.google.com
  • IP address
    216.239.36.10
    Host
    ns3.google.com
  • IP address
    216.239.38.10
    Host
    ns4.google.com
  • IP address
    216.239.34.10
    Host
    ns2.google.com
DNS zone
blogspot.com

Page quality

Layout shift (CLS)
0.367
SEO score
50
Speed Index, s
4.17
First Contentful Paint (FCP), s
2.36
Largest Contentful Paint (LCP), s
11.02
Total Blocking Time (TBT), ms
38
Performance score
52
Accessibility score
59
Best practices score
81

Location

IP address
2a00:1450:4001:c21::84
ASN
15169
Organization
Google LLC
City
Frankfurt am Main
Country
DE

TLS certificate

Subject alternative names
  • misc-sni.blogspot.com
  • blogspot.ae
  • *.blogspot.ae
  • blogspot.al
  • *.blogspot.al
  • blogspot.am
  • *.blogspot.am
  • blogspot.ba
  • *.blogspot.ba
  • blogspot.be
  • *.blogspot.be
  • blogspot.bg
  • *.blogspot.bg
  • blogspot.ca
  • *.blogspot.ca
  • blogspot.ch
  • *.blogspot.ch
  • blogspot.cl
  • *.blogspot.cl
  • blogspot.co.at
  • *.blogspot.co.at
  • blogspot.co.id
  • *.blogspot.co.id
  • blogspot.co.il
  • *.blogspot.co.il
  • blogspot.co.ke
  • *.blogspot.co.ke
  • blogspot.co.nz
  • *.blogspot.co.nz
  • blogspot.co.uk
  • *.blogspot.co.uk
  • blogspot.co.za
  • *.blogspot.co.za
  • blogspot.com
  • *.blogspot.com
  • blogspot.com.ar
  • *.blogspot.com.ar
  • blogspot.com.au
  • *.blogspot.com.au
  • blogspot.com.br
  • *.blogspot.com.br
  • blogspot.com.by
  • *.blogspot.com.by
  • blogspot.com.co
  • *.blogspot.com.co
  • blogspot.com.cy
  • *.blogspot.com.cy
  • blogspot.com.ee
  • *.blogspot.com.ee
  • blogspot.com.eg
Key size, bits
256
Certificate chain
  • misc-sni.blogspot.com
  • WE2
  • GTS Root R4
Issuer
Google Trust Services / WE2
Serial
BE9362B229C6A5E7105430FBFB588354
SHA-256
410aa334dd10ce86a20d47f491f7acecd522eb9eb5c9cfa584840c3ad95eef27
Subject
misc-sni.blogspot.com
Valid until
Valid from

DNS records

A
  • 142.251.20.132
AAAA
  • 2a00:1450:4001:c21::84
CNAME
  • blogspot.l.googleusercontent.com

DNSSEC

DS record
Yes
RRSIG
No
DNSKEY
Yes

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
1; mode=block
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a00:1450:4001:c21::84
IP version
6

Redirects

Redirect chain
  • https://ivana-alawijosjis.blogspot.com

Technology stack

Technologies
  • Blogger
  • Python
  • Java
  • Bootstrap 3.3.7
  • OpenGSE
  • Cloudflare
  • Google Hosted Libraries
  • cdnjs
  • Modernizr 2.7.1
  • jQuery 1.12.1
  • Google Font API
  • Font Awesome 4.3.0
  • Open Graph
  • HTTP/3

Page links

External link addresses
  • https://bountymove.com/
External links
1

HTTP headers

Response headers
Server
GSE
Content-Type
text/html; charset=UTF-8
X-Content-Type-Options
nosniff
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 1; Domain: blogspot.com; Issuers: pki.goog
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Crawler rules
Allow: /; Agents: Mediapartners-Google, *; Present: ✓; Disallow: /search, /share-widget; Sitemaps: https://ivana-alawijosjis.blogspot.com/sitemap.xml
Sitemap
URLS: https://ivana-alawijosjis.blogspot.com/2026/11/done.html; Present: ✓; URL count: 1; Lastmod max: 2026-11-13T23:48:52Z; Lastmod min: 2026-11-13T23:48:52Z
Page title and metadata
Title: Ivana Alawi 
 Espesyal sa Facebook; Robots: noindex, nofollow; Ogimage: https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEggkRlJWASHbxL2DY2y94v85lwPNkAsTzVhVjPqS6HNUuQa_iWXzZxupuBYDcSRD7zMRBPXlWUbTIng7cU69_7cVPIO0RdpexEPW7VbFsYJVrNuSw_4QEh9b9fNYEG5kRTXxK86fbZ8T0GZOyFXd_FDbUJ1cq6I14qE1JPsBRCc68yf7FO_S8zws1jbY639/s722/Screenshot_110.png
Trackers
Requests: 29; Trackers: (Name: Bootstrap CDN; Company: BootstrapCDN; Country: US; Category: Hosting; Requests: 3), (Name: Cloudflare; Company: Cloudflare; Country: US; Category: Hosting; Requests: 1), (Name: Google APIs; Company: Google; Country: US; Category: Hosting; Requests: 3), (Name: Google Fonts; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Google User Content; Company: Google; Country: US; Category: Hosting; Requests: 20), (Name: blogspot.com; Company: Google; Country: US; Category: Misc; Requests: 1), (Name: Google+ Platform; Company: Google; Country: US; Category: Social Media; Requests: 2)
Forms and mixed content
No sri: https://apis.google.com/js/platform.js, https://apis.google.com/js/plusone.js, https://ajax.googleapis.com/ajax/libs/jquery/1.12.1/jquery.min.js, https://cdnjs.cloudflare.com/ajax/libs/modernizr/2.7.1/modernizr.min.js; Third party scripts: 5
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 242; Download: 0; Response ms: 280
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
Carbon
Bytes: 33654; Co2 grams: 0.0012; Cleaner than: 46
DNS server
NS: (IP: 216.239.32.10; Host: ns1.google.com), (IP: 216.239.36.10; Host: ns3.google.com), (IP: 216.239.38.10; Host: ns4.google.com), (IP: 216.239.34.10; Host: ns2.google.com); Zone: blogspot.com
Quality
Cls: 0.367; Seo: 50; Si s: 4.17; Fcp s: 2.36; Lcp s: 11.02; Tbt ms: 38; Performance: 52; Accessibility: 59; Best practices: 81
Location
IP: 2a00:1450:4001:c21::84; ASN: 15169; Org: Google LLC; City: Frankfurt am Main; Country: DE
SSL
San: misc-sni.blogspot.com, blogspot.ae, *.blogspot.ae, blogspot.al, *.blogspot.al, blogspot.am, *.blogspot.am, blogspot.ba, *.blogspot.ba, blogspot.be, *.blogspot.be, blogspot.bg, *.blogspot.bg, blogspot.ca, *.blogspot.ca, blogspot.ch, *.blogspot.ch, blogspot.cl, *.blogspot.cl, blogspot.co.at, *.blogspot.co.at, blogspot.co.id, *.blogspot.co.id, blogspot.co.il, *.blogspot.co.il, blogspot.co.ke, *.blogspot.co.ke, blogspot.co.nz, *.blogspot.co.nz, blogspot.co.uk, *.blogspot.co.uk, blogspot.co.za, *.blogspot.co.za, blogspot.com, *.blogspot.com, blogspot.com.ar, *.blogspot.com.ar, blogspot.com.au, *.blogspot.com.au, blogspot.com.br, *.blogspot.com.br, blogspot.com.by, *.blogspot.com.by, blogspot.com.co, *.blogspot.com.co, blogspot.com.cy, *.blogspot.com.cy, blogspot.com.ee, *.blogspot.com.ee, blogspot.com.eg; Bits: 256; Chain: misc-sni.blogspot.com, WE2, GTS Root R4; Issuer: Google Trust Services / WE2; Serial: BE9362B229C6A5E7105430FBFB588354; SHA256: 410aa334dd10ce86a20d47f491f7acecd522eb9eb5c9cfa584840c3ad95eef27; Subject: misc-sni.blogspot.com; Valid to: 2027-01-26T08:28:11Z; Valid from: 2026-11-03T08:28:12Z
DNS records
A: 142.251.20.132; Aaaa: 2a00:1450:4001:c21::84; Cname: blogspot.l.googleusercontent.com
Dnssec
Ds: ✓; Rrsig: ✗; Dnskey: ✓
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: 1; mode=block; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 2a00:1450:4001:c21::84; Family: 6
Redirects
Chain: https://ivana-alawijosjis.blogspot.com
Tech stack
Technologies: Blogger, Python, Java, Bootstrap 3.3.7, OpenGSE, Cloudflare, Google Hosted Libraries, cdnjs, Modernizr 2.7.1, jQuery 1.12.1, Google Font API, Font Awesome 4.3.0, Open Graph, HTTP/3
Page links
External: https://bountymove.com/; External count: 1
HTTP headers
Headers: Server: GSE; Content type: text/html; charset=UTF-8; X content type options: nosniff

Questions about ivana-alawijosjis.blogspot.com

Is ivana-alawijosjis.blogspot.com legit?

PhishDestroy rates ivana-alawijosjis.blogspot.com as critical risk (evidence score 84/100) from the recorded evidence; it was first recorded on 2026-11-22. Stored VirusTotal result: 8/92 engines flagged. Analysis time (as stored): 2026-11-21 18:07 UTC. Retrieved (as stored): 2026-11-22 15:29 UTC. Listed by external blocklists: OpenPhish. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is ivana-alawijosjis.blogspot.com safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on ivana-alawijosjis.blogspot.com. A confirmed blockchain transaction cannot be reversed.

What should I do if I used ivana-alawijosjis.blogspot.com?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matches1 external + PhishDestroy list · OpenPhish · PhishDestroy 1
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Page captures (3)

All capture links and hashes (3)

Domain details

Domain
Platform provider Google Domains US(US)
Abuse contactabuse@google.com
HTTP Status200
Technical detailsProvenance & timestamps
First Detected2026-11-22
Submitted URLhttp://ivana-alawijosjis.blogspot.com/
Favicon Hash
Observed page title
Ivana Alawi Espesyal sa Facebook
TLS Certificate
Issued by Google Trust Services / WE2 · stored validity ends in 64 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
142.251.127.132
Server header
GSE

Nameservers 4

  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com

TLS certificate

Issuer
Google Trust Services / WE2
Valid from
2026-11-03 08:28:12
Valid until
2027-01-26 08:28:11
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint410aa334dd10ce86a20d47f491f7acecd522eb9eb5c9cfa584840c3ad95eef27
Certificate names · 50 SANs
  • misc-sni.blogspot.com
  • blogspot.ae
  • *.blogspot.ae
  • blogspot.al
  • *.blogspot.al
  • blogspot.am
  • *.blogspot.am
  • blogspot.ba
  • *.blogspot.ba
  • blogspot.be
  • *.blogspot.be
  • blogspot.bg
  • *.blogspot.bg
  • blogspot.ca
  • *.blogspot.ca
  • blogspot.ch
  • *.blogspot.ch
  • blogspot.cl
  • *.blogspot.cl
  • blogspot.co.at
  • *.blogspot.co.at
  • blogspot.co.id
  • *.blogspot.co.id
  • blogspot.co.il
  • *.blogspot.co.il
  • blogspot.co.ke
  • *.blogspot.co.ke
  • blogspot.co.nz
  • *.blogspot.co.nz
  • blogspot.co.uk
  • *.blogspot.co.uk
  • blogspot.co.za
  • *.blogspot.co.za
  • blogspot.com
  • *.blogspot.com
  • blogspot.com.ar
  • *.blogspot.com.ar
  • blogspot.com.au
  • *.blogspot.com.au
  • blogspot.com.br
  • *.blogspot.com.br
  • blogspot.com.by
  • *.blogspot.com.by
  • blogspot.com.co
  • *.blogspot.com.co
  • blogspot.com.cy
  • *.blogspot.com.cy
  • blogspot.com.ee
  • *.blogspot.com.ee
  • blogspot.com.eg

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

VirusTotal Analysis

8 / 92 security vendors flagged this domain
View on VT
Last analyzed
ESET
G-Data
Sophos
Fortinet
SOCRadar
LevelBlue
OpenPhish
BitDefender
PageSpeed (mobile): 56

Google PageSpeed Insights — mobile performance audit of ivana-alawijosjis.blogspot.com ·

56
Needs Work
Performance
FCP
2.31 s
First Contentful Paint
LCP
13.67 s
Largest Contentful Paint
CLS
0.291
Cumulative Layout Shift
TBT
27 ms
Total Blocking Time
SI
2.56 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data73
Open complete records

Captured network requests

Network requests: 40 SHA-256 hashes: 35 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-22 15:28 UTC.

Open this scan on URLScan 01a203dd-3a4c-72e9-aad1-3e908ce35775 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations0

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

No retained observations are recorded.

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

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

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    ivana-alawijosjis.blogspot.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Automated brand label: Facebook · Forensic Evidence Collected recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

3 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+9608 d 20 h
  3. Added to PhishDestroy+21 h 19 min
  1. Added to PhishDestroy

    ivana-alawijosjis.blogspot.com

    same minute
  2. URLScan

    Page captured

    +21 h 19 min
  3. VirusTotal

    8/92 engine detections

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.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface 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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

ivana-alawijosjis.blogspot.com

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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

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

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