Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 18/92 engines flagged. malicious: 16. suspicious: 2. Analysis time (as stored): 2026-11-01T14:10:40Z. Retrieved (as stored): 2026-11-02T11:50:55Z. Listed by external blocklists: Phishunt. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
r-facebook.blogspot.com favicon

r-facebook.blogspot.com

In short

The screenshot of r-facebook.blogspot.com shows a Blogger blog page with the heading FACEBOOK. A post dated Sabtu, 27 Februari 2010 is attributed to King Rosyad and contains the text "I'm a king!" alongside a small profile image. A Beranda button and a Lihat versi web link appear below the post. An author section labeled Mengenal Saya shows A.S.ROSYAD with the text "Yeah..im cool..." and a Lihat profil lengkapku link, and the footer reads Diberdayakan oleh Blogger.

“FACEBOOK”

Review the evidence
Registrar
United StatesGoogle Domains
Resolved IP
Germany142.251.14.132Google LLC
First observed
Nov 2, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 18/92 Stored blocklist matches: 1
VirusTotal
18 / 92
engine detections ·
Blocklist matches
1
Phishunt
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
5
open gallery
Nov 2, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded r-facebook.blogspot.com on 2026-11-02. Stored VirusTotal result: 18/92 engines flagged. malicious: 16. suspicious: 2. Analysis time (as stored): 2026-11-01T14:10:40Z. Retrieved (as stored): 2026-11-02T11:50:55Z. Listed by external blocklists: Phishunt. Risk: critical (100/100). Registrar: Google Domains. Status: Last known active. Hosting: Google LLC. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
18 / 92
Blocklist matches
1
Hosting
Germany142.251.14.132Google LLC
Registrar
United StatesGoogle Domains
Page captures
5
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-11-02T11:42:29Z
SHA-256: 7315bbdaeb125c54f25c2c91cff5be568c145ef54586ac09cbe640dcb0ab7406

PhishDestroy analysis, reviewed version

The screenshot of r-facebook.blogspot.com shows a Blogger blog page with the heading FACEBOOK. A post dated Sabtu, 27 Februari 2010 is attributed to King Rosyad and contains the text "I'm a king!" alongside a small profile image. A Beranda button and a Lihat versi web link appear below the post. An author section labeled Mengenal Saya shows A.S.ROSYAD with the text "Yeah..im cool..." and a Lihat profil lengkapku link, and the footer reads Diberdayakan oleh Blogger.

The stored VirusTotal domain result reports 18 detections out of 92 engines. ESET reported "suspicious"; VIPRE reported "phishing".

Source evidenceVirusTotal 18 / 92 7 sources

VirusTotal

18 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
16
Suspicious
2
Undetected
30

Vendor labels

ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
Webroot
malicious
AlphaSOC
suspicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
Kaspersky
phishing
LevelBlue
phishing
Gridinsoft
phishing
MalwareURL
phishing
BitDefender
phishing
Criminal IP
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    CNAME
    Value
    blogspot.l.googleusercontent.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2607:f8b0:4001:c70::84
  • TTL, seconds
    300
    Type
    A
    Value
    192.178.209.132

DNS records observed

JARM fingerprint

27d40d40d29d40d1dc42d43d00041ded961c16c68658e95145597cf992c36c

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
Issuer
Google Trust Services / WE2
Serial
df5f64f180a7d2ab12c150dcb1b1c5ce
SHA-256
fadd233a6c56e1e80d8f04b45a10d6c9e3ad14ba6d28401c13599390461a9cfd
Subject
misc-sni.blogspot.com
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
  • serverDeleteProhibited
  • serverTransferProhibited
  • serverUpdateProhibited
Nameservers
  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 16,
    "suspicious": 2,
    "undetected": 30
}
Vendor labels
{
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "AlphaSOC": "suspicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "Criminal IP": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2000-07-31T21:38:58Z
Expires
2027-07-31T21:38:58Z
Updated
2026-06-29T10:34:06Z
First seen
2026-07-13T23:15:06Z
DNS records
[
    {
        "ttl": 300,
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2607:f8b0:4001:c70::84"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "192.178.209.132"
    }
]
Dns at
2026-11-01T14:15:54Z
Jarm
27d40d40d29d40d1dc42d43d00041ded961c16c68658e95145597cf992c36c
Certificate
{
    "san": [
        "misc-sni.blogspot.com",
        "blogspot.ae",
        "*.blogspot.ae",
        "blogspot.al",
        "*.blogspot.al",
        "blogspot.am",
        "*.blogspot.am",
        "blogspot.ba",
        "*.blogspot.ba",
        "blogspot.be"
    ],
    "issuer": "Google Trust Services / WE2",
    "serial": "df5f64f180a7d2ab12c150dcb1b1c5ce",
    "sha256": "fadd233a6c56e1e80d8f04b45a10d6c9e3ad14ba6d28401c13599390461a9cfd",
    "subject": "misc-sni.blogspot.com",
    "valid_to": "2026-12-30T19:08:51Z",
    "valid_from": "2026-10-07T19:08:52Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2000-07-31T07:00:00Z",
    "updated": "2026-06-29T10:34:06Z",
    "expires": "2027-07-31T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited",
        "serverDeleteProhibited",
        "serverTransferProhibited",
        "serverUpdateProhibited"
    ],
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ],
    "dnssec": "unsigned"
}
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
scope
unknown
result_state
observed
numerator
18
denominator
92
malicious
null
suspicious
null
vendors
["Criminal IP","alphaMountain.ai","AlphaSOC","BitDefender","ESET","Emsisoft","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","LevelBlue","Lionic","MalwareURL","Netcraft","Sophos","VIPRE","Webroot"]
observed_at
2026-11-01 14:10:40
checked_at
2026-11-02 12:50:58
fetched_at
2026-11-02 11:50:59
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

318c74a9-49f7-4a27-b2d6-b7bd1f92ae02

Final URL

https://r-facebook.blogspot.com/

HTTP response

200

Navigation history

  • URL
    https://r-facebook.blogspot.com/
    Status
    200

DOM structure hash

3ffd3fe6970c46521840b857e3ab84335e96a4587e91f224e603b74efbb8a4c8

Document hash

931954f6a5136b14f901015fe576a9da01760e81a8ae15fbd6b884815123291a

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>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
    r-facebook.blogspot.com
    Type
    CNAME
    Value
    blogspot.l.googleusercontent.com
  • Name
    r-facebook.blogspot.com
    Type
    CNAME
    Value
    blogspot.l.googleusercontent.com

DNSSEC valid

No

IP address

127.0.1.18

127.0.1.18 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com
Original source fields · JSON
Uuid
318c74a9-49f7-4a27-b2d6-b7bd1f92ae02
Final url
https://r-facebook.blogspot.com/
Status
200
History
[
    {
        "url": "https://r-facebook.blogspot.com/",
        "status": 200
    }
]
DOM structure hash
3ffd3fe6970c46521840b857e3ab84335e96a4587e91f224e603b74efbb8a4c8
Document hash
931954f6a5136b14f901015fe576a9da01760e81a8ae15fbd6b884815123291a
Phishing v2
[
    "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": "r-facebook.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "name": "r-facebook.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    }
]
Dnssec valid
false
Ip
127.0.1.18

127.0.1.18 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

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"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious

SHA-256 b6f87fb08379eb27d1358ccb49afa9744ae63190226e4c3b473653144f927f39

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a19c11-4cc7-740a-83d5-529c5df0b6f4

Final URL

https://r-facebook.blogspot.com/

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://r-facebook.blogspot.com/
    From
    http://r-facebook.blogspot.com/
    Status
    307
  • To
    https://r-facebook.blogspot.com/
    From
    https://r-facebook.blogspot.com/
    Status
    302

IP address

2a00:1450:4001:c0f::84

Contacted domains

  • www.blogger.com
  • blogger.googleusercontent.com
  • pagead2.googlesyndication.com

Contacted IP addresses

  • 142.251.20.132
  • 142.251.20.155
  • 2a00:1450:4001:c21::84
  • 2a00:1450:4001:c0f::bf
  • 2a00:1450:4001:c0f::84

Autonomous systems (ASN)

  • 15169

Server countries

  • US
  • DE

Linked domains

  • www.blogger.com

Document hash

b6f87fb08379eb27d1358ccb49afa9744ae63190226e4c3b473653144f927f39

JavaScript globals

  • setAttributeOnload
  • 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
  • BLOG_BASE_IMAGE_URL
  • BLOG_LANG_DIR

TLS session and 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
Cipher
AES_128_GCM
Issuer
WE2
Subject
misc-sni.blogspot.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

111

Registered domain age, days

111

Certificate age, days

25

Certificate validity, days

83

Page requests

9

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • facebook
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Facebook
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
GSE
Content-type
text/html; charset=UTF-8
X-content-type-options
nosniff
Original source fields · JSON
Uuid
01a19c11-4cc7-740a-83d5-529c5df0b6f4
Final url
https://r-facebook.blogspot.com/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://r-facebook.blogspot.com/",
        "from": "http://r-facebook.blogspot.com/",
        "status": 307
    },
    {
        "to": "https://r-facebook.blogspot.com/",
        "from": "https://r-facebook.blogspot.com/",
        "status": 302
    }
]
Ip
2a00:1450:4001:c0f::84
Contacted domains
[
    "www.blogger.com",
    "blogger.googleusercontent.com",
    "pagead2.googlesyndication.com"
]
Contacted IP addresses
[
    "142.251.20.132",
    "142.251.20.155",
    "2a00:1450:4001:c21::84",
    "2a00:1450:4001:c0f::bf",
    "2a00:1450:4001:c0f::84"
]
Asns
[
    "15169"
]
Countries
[
    "US",
    "DE"
]
Linked domains
[
    "www.blogger.com"
]
Document hash
b6f87fb08379eb27d1358ccb49afa9744ae63190226e4c3b473653144f927f39
Globals
[
    "setAttributeOnload",
    "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",
    "BLOG_BASE_IMAGE_URL",
    "BLOG_LANG_DIR"
]
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": "WE2",
    "subject": "misc-sni.blogspot.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-30T19:08:51Z",
    "valid_from": "2026-10-07T19:08:52Z"
}
Domain age days
111
Apex age days
111
Tls age days
25
Tls valid days
83
Requests
9
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "facebook"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Facebook"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "GSE",
    "content-type": "text/html; charset=UTF-8",
    "x-content-type-options": "nosniff"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a19c11-4cc7-740a-83d5-529c5df0b6f4
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-11-02T12:02:41Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-11-02T12:02:41Z
source_timestamp
2026-11-02 13:02:41
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
r-facebook.blogspot.com: Blogger Blog Page Titled FACEBOOK
ai_description
PhishDestroy records r-facebook.blogspot.com as a Blogger blog page titled FACEBOOK, showing a 2010 post by King Rosyad and an author profile section.
ai_summary
The screenshot of r-facebook.blogspot.com shows a Blogger blog page with the heading FACEBOOK. A post dated Sabtu, 27 Februari 2010 is attributed to King Rosyad and contains the text "I'm a king!" alongside a small profile image. A Beranda button and a Lihat versi web link appear below the post. An author section labeled Mengenal Saya shows A.S.ROSYAD with the text "Yeah..im cool..." and a Lihat profil lengkapku link, and the footer reads Diberdayakan oleh Blogger. The stored VirusTotal domain result reports 18 detections out of 92 engines. ESET reported "suspicious"; VIPRE reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-02 12:54:25
revision
70e60d62cfe6706575648088ab73389e54a29e3f55a13f3fef7b31c71093ca60
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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: 23 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

User agents
  • Mediapartners-Google
  • *
Present
Yes
Sitemap URLs
  • https://r-facebook.blogspot.com/sitemap.xml

Sitemap

Present
Yes
URL count
1

Page title and metadata

Open Graph URL
http://r-facebook.blogspot.com/
Page title
FACEBOOK
Author
Your Name/Your Company
Indexing directives
all
Open Graph title
FACEBOOK
Keywords
Put keywords separated by commas here
Generator
blogger
Description
Put your blog Description here
Canonical URL
http://r-facebook.blogspot.com/

Trackers

Requests
38
Observed services
  • Name
    Google Syndication
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    4
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google User Content
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    7
  • Name
    blogspot.com
    Company
    Google
    Country
    US
    Category
    Misc
    Requests
    19
  • Name
    AddToAny
    Company
    AddToAny
    Country
    US
    Category
    Social Media
    Requests
    4
  • Name
    Google+ Platform
    Company
    Google
    Country
    US
    Category
    Social Media
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://174.132.149.5/~tmwwtw/smellslikefacebook/js/script.js
  • https://apis.google.com/js/platform.js
  • https://static.addtoany.com/menu/page.js
  • https://www.blogger.com/static/v1/widgets/207833187-widgets.js
Third-party scripts
4

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
20
Waiting
239
Connection
6
Download
16
Response time, ms
283

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
33000
CO₂, grams
0.0012
Cleaner than, %
46

DNS servers

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

Location

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

TLS certificate

Issuer
Google Trust Services / WE2
Subject
misc-sni.blogspot.com

DNS records

A
  • 142.251.110.132
AAAA
  • 2a00:1450:4001:c1f::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:c1f::84
IP version
6

Redirects

Redirect chain
  • https://r-facebook.blogspot.com

Page links

External link addresses
  • https://draft.blogger.com/profile/05965454731972662346
  • https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj4LjQ6YB7w0V0KokNalOiWjE93TkLeImTQTX5so4KQ8IuX50QfXXI-XYACd-a2gmsiZ_P-g_W6wUCSMk7uLtBHKJ1BfWCZKfJrvKJt-QWVR9dd523BX96x2AmQuDp49m2lVIhT-D2B9g/
  • http://www.addtoany.com/share_save
  • https://draft.blogger.com/post-edit.g
  • http://nazieb.com/
  • http://bloggertemplateslibrary.blogspot.com/
External links
6
Internal links
11

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
{
    "agents": [
        "Mediapartners-Google",
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://r-facebook.blogspot.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 1
}
Page title and metadata
{
    "ogUrl": "http://r-facebook.blogspot.com/",
    "title": "FACEBOOK",
    "author": "Your Name/Your Company",
    "robots": "all",
    "ogTitle": "FACEBOOK",
    "keywords": "Put keywords separated by commas here",
    "generator": "blogger",
    "description": "Put your blog Description here",
    "canonicalUrl": "http://r-facebook.blogspot.com/"
}
Trackers
{
    "requests": 38,
    "trackers": [
        {
            "name": "Google Syndication",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Google APIs",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 4
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google User Content",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 7
        },
        {
            "name": "blogspot.com",
            "company": "Google",
            "country": "US",
            "category": "Misc",
            "requests": 19
        },
        {
            "name": "AddToAny",
            "company": "AddToAny",
            "country": "US",
            "category": "Social Media",
            "requests": 4
        },
        {
            "name": "Google+ Platform",
            "company": "Google",
            "country": "US",
            "category": "Social Media",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://174.132.149.5/~tmwwtw/smellslikefacebook/js/script.js",
        "https://apis.google.com/js/platform.js",
        "https://static.addtoany.com/menu/page.js",
        "https://www.blogger.com/static/v1/widgets/207833187-widgets.js"
    ],
    "third_party_scripts": 4
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 20,
        "wait": 239,
        "connect": 6,
        "download": 16
    },
    "response_ms": 283
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 33000,
    "co2_grams": 0.0012,
    "cleaner_than": 46
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.34.10",
            "host": "ns2.google.com"
        },
        {
            "ip": "216.239.38.10",
            "host": "ns4.google.com"
        },
        {
            "ip": "216.239.36.10",
            "host": "ns3.google.com"
        },
        {
            "ip": "216.239.32.10",
            "host": "ns1.google.com"
        }
    ],
    "zone": "blogspot.com"
}
Location
{
    "ip": "2a00:1450:4001:c1f::84",
    "asn": "15169",
    "org": "Google LLC",
    "city": "Frankfurt am Main",
    "country": "DE"
}
Ssl
{
    "issuer": "Google Trust Services / WE2",
    "subject": "misc-sni.blogspot.com"
}
DNS records
{
    "A": [
        "142.251.110.132"
    ],
    "AAAA": [
        "2a00:1450:4001:c1f::84"
    ],
    "CNAME": [
        "blogspot.l.googleusercontent.com"
    ]
}
Dnssec
{
    "ds": true,
    "rrsig": false,
    "dnskey": true
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": "1; mode=block",
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2a00:1450:4001:c1f::84",
    "family": 6
}
Redirects
{
    "chain": [
        "https://r-facebook.blogspot.com"
    ]
}
Page links
{
    "external": [
        "https://draft.blogger.com/profile/05965454731972662346",
        "https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj4LjQ6YB7w0V0KokNalOiWjE93TkLeImTQTX5so4KQ8IuX50QfXXI-XYACd-a2gmsiZ_P-g_W6wUCSMk7uLtBHKJ1BfWCZKfJrvKJt-QWVR9dd523BX96x2AmQuDp49m2lVIhT-D2B9g/",
        "http://www.addtoany.com/share_save",
        "https://draft.blogger.com/post-edit.g",
        "http://nazieb.com/",
        "http://bloggertemplateslibrary.blogspot.com/"
    ],
    "external_count": 6,
    "internal_count": 11
}
HTTP headers
{
    "headers": {
        "server": "GSE",
        "content-type": "text/html; charset=UTF-8",
        "x-content-type-options": "nosniff"
    }
}

Questions about r-facebook.blogspot.com

Is r-facebook.blogspot.com legit?

PhishDestroy rates r-facebook.blogspot.com as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-02. Stored VirusTotal result: 18/92 engines flagged. malicious: 16. suspicious: 2. Analysis time (as stored): 2026-11-01T14:10:40Z. Retrieved (as stored): 2026-11-02T11:50:55Z. Listed by external blocklists: Phishunt. Treat the site as unsafe.

Is r-facebook.blogspot.com safe to connect a wallet?

This report does not record which wallet requests r-facebook.blogspot.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used r-facebook.blogspot.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you 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 matchesPhishDestroy · Phishunt · no match in the other 10 2
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Checked, no match

Last checked

Stored Capture · 5 captures

URLScan · 2026-11-02 1 / 5 Used in the analysis Source file SHA-256: 7315bbdaeb125c54f25c2c91cff5be568c145ef54586ac09cbe640dcb0ab7406 SHA-256 of the prepared copy given to the model: d42d29b29e5cbda7a499cc6e0d5c4b10f1fc32198be7e3f5c0a8865d7efd9568
SourceURLScan · 2026-11-02
Recorded
StateStored capture
HTTP status200
Final URLhttps://r-facebook.blogspot.com/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)

Domain details

Domain
Platform provider Google Domains US(US)
Abuse contactnetwork-abuse@google.com, abuse@google.com
Hosting abuse contact network-abuse@google.com, abuse@google.com Google LLC · AS15169
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 2, 2026
DOM Analysisanalyzed Nov 2, 2026score 10/1001 brand signal
Submitted URLhttp://r-facebook.blogspot.com/
Observed page title
FACEBOOK
Automated brand references
Facebook
TLS Certificate
Issued by WE2 · stored validity ends in 58 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany142.251.14.132
Network ASN
AS15169
Organization
Google LLC
Observed location
GermanyFrankfurt am Main, DE
Server header
GSE

Location describes the IP network.

TLS certificate

Issuer
WE2
Valid from
2026-10-07 19:08:52
Valid until
2026-12-30 19:08:51
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintfadd233a6c56e1e80d8f04b45a10d6c9e3ad14ba6d28401c13599390461a9cfd
Certificate names · 10 SANs
  • misc-sni.blogspot.com
  • blogspot.ae
  • *.blogspot.ae
  • blogspot.al
  • *.blogspot.al
  • blogspot.am
  • *.blogspot.am
  • blogspot.ba
  • *.blogspot.ba
  • blogspot.be

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.14.132rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
ESET
VIPRE
G-Data
Lionic
Sophos
Webroot
AlphaSOC
Emsisoft
Fortinet
Netcraft
Kaspersky
LevelBlue
Gridinsoft
MalwareURL
BitDefender
Criminal IP
alphaMountain.ai
Forcepoint ThreatSeeker
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of r-facebook.blogspot.com · checked Nov 2, 2026

100
Good
Performance
FCP
1.54 s
First Contentful Paint
LCP
1.54 s
Largest Contentful Paint
CLS
0.03
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.54 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.

Captured network requests

Network requests: 9 SHA-256 hashes: 8 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-02 11:48 UTC.

Open this scan on URLScan 01a19c11-4cc7-740a-83d5-529c5df0b6f4 ↗

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 observations2

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.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:44:24.000000
    Evidence SHA-256
    5e5f159cee5d137e576aefc6f6596b3df124f8a14888d64a9332883b81bbe0e1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 12:44:24
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:44:24.000000
    Evidence SHA-256
    5e5f159cee5d137e576aefc6f6596b3df124f8a14888d64a9332883b81bbe0e1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 12:44:24
    Evidence reason

Threat Response Pipeline

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

Recorded events: 10. 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: 1 of 1
  • Threat Ingested
    r-facebook.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 · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 18/92
  • Blocklist Detection
    Found in blocklists: Phishunt
  • Automated brand label: Facebook
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. Cloudflare Radar

    Phishing

    View source
  2. Added to PhishDestroy

    r-facebook.blogspot.com

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    18/92 engine detections

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

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
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.

r-facebook.blogspot.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 18 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report WOT ScamAdviser 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
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?

3 evidence signal groups linked Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. 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.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • 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

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

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.

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