Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 19. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
facebook-verification-system5.blogspot.com favicon

facebook-verification-system5.blogspot.com

In short

PhishDestroy records facebook-verification-system5.blogspot.com, a page claiming Facebook is deleting unverified profiles.

“facebook deleting all fake profiles”

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

Analysis

Domain summary

PhishDestroy records facebook-verification-system5.blogspot.com, a page claiming Facebook is deleting unverified profiles.

Critical
Status
Last known active
VirusTotal
19 / 92
Blocklist matches
1
Scam type (automated label)
Impersonation
Hosting
Germany142.251.13.132Google LLC
Registrar
United StatesGoogle Domains
Page captures
8
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page at facebook-verification-system5.blogspot.com carries the title "facebook deleting all fake profiles" and a meta description urging readers to verify their location before their account is removed, adding that one account was already verified. The visible screenshot shows only a German Google cookie consent banner with "WEITERE INFORMATIONEN" and "OK" buttons over an otherwise empty page, so the verification interaction described in the metadata is not visible in this capture.

The stored VirusTotal result reports 19 detections out of 92 engines.

Source evidenceVirusTotal 19 / 92 7 sources

VirusTotal

19 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
19
Suspicious
0
Undetected
30

Vendor labels

ESET
phishing
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
URLQuery
malicious
Kaspersky
phishing
LevelBlue
phishing
OpenPhish
phishing
Gridinsoft
phishing
MalwareURL
phishing
BitDefender
phishing
Chong Lua Dao
malicious
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
    A
    Value
    74.125.69.132
  • TTL, seconds
    300
    Type
    CNAME
    Value
    blogspot.l.googleusercontent.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2607:f8b0:4001:c08::84

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
9d5a60aa1a77b2e30ad083111463b97f
SHA-256
96af029a35a29461434960b48ba2154af0c39c2d7eb0c4b553a22552f01a76ff
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": 43,
    "malicious": 19,
    "suspicious": 0,
    "undetected": 30
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "OpenPhish": "phishing",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "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
2024-03-05T17:02:30Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "74.125.69.132"
    },
    {
        "ttl": 300,
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2607:f8b0:4001:c08::84"
    }
]
Dns at
2026-10-17T14:37:44Z
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": "9d5a60aa1a77b2e30ad083111463b97f",
    "sha256": "96af029a35a29461434960b48ba2154af0c39c2d7eb0c4b553a22552f01a76ff",
    "subject": "misc-sni.blogspot.com",
    "valid_to": "2026-12-11T20:01:30Z",
    "valid_from": "2026-09-18T20:01:31Z"
}
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 source record · 19 malicious + 0 suspicious / 92 · 2026-10-17 14:37:27 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-17T14:37:27Z
fetched_at
2026-10-26T01:00:19Z
stats
{"timeout":0,"harmless":43,"malicious":19,"suspicious":0,"undetected":30}

URLScan

Malicious

SHA-256 81bc271547ea1bcf34b69f693730f4e0c2e31a0a491f524a7337a62043da5f71

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a175a8-37c5-77d0-969c-9584cc2e81dc

Final URL

https://facebook-verification-system5.blogspot.com/

HTTP response

200

Redirect type

same-domain

Redirects

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

IP address

172.253.63.132

Reverse DNS (PTR)

bi-in-f132.1e100.net

Contacted domains

  • www.blogger.com
  • resources.blogblog.com
  • pagead2.googlesyndication.com

Contacted IP addresses

  • 172.253.63.191
  • 142.251.16.157
  • 64.233.180.191
  • 172.253.63.132

Autonomous systems (ASN)

  • 15169

Server countries

  • US

Linked domains

  • www.blogger.com

Document hash

be0e0b2a19a252c3301c2a395aa91f981c9dd1ec1d72057cae68cb556df99d76

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

95

Registered domain age, days

95

Certificate age, days

27

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
01a175a8-37c5-77d0-969c-9584cc2e81dc
Final url
https://facebook-verification-system5.blogspot.com/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://facebook-verification-system5.blogspot.com/",
        "from": "http://facebook-verification-system5.blogspot.com/",
        "status": 307
    },
    {
        "to": "https://facebook-verification-system5.blogspot.com/",
        "from": "https://facebook-verification-system5.blogspot.com/",
        "status": 302
    }
]
Ip
172.253.63.132
Ptr
bi-in-f132.1e100.net
Contacted domains
[
    "www.blogger.com",
    "resources.blogblog.com",
    "pagead2.googlesyndication.com"
]
Contacted IP addresses
[
    "172.253.63.191",
    "142.251.16.157",
    "64.233.180.191",
    "172.253.63.132"
]
Asns
[
    "15169"
]
Countries
[
    "US"
]
Linked domains
[
    "www.blogger.com"
]
Document hash
be0e0b2a19a252c3301c2a395aa91f981c9dd1ec1d72057cae68cb556df99d76
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-21T18:40:33Z",
    "valid_from": "2026-09-28T18:40:34Z"
}
Domain age days
95
Apex age days
95
Tls age days
27
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 · 2026-10-26 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a175a8-37c5-77d0-969c-9584cc2e81dc
score
100
malicious
true
result_at
2026-10-26T04:30:13Z
enriched_at
2026-10-26T09:12:33Z
source_timestamps
{"urlscan_result_at":"2026-10-26 05:30:13","urlscan_enriched_at":"2026-10-26 10:12:33"}
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

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

68 / 100 · heuristic score · 1 brand reference · 1 classification

Open report
Separate monitor score · 10 / 100 · 2026-10-26T03:20:13Z

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-10-26T03:20:13Z
source_timestamp
2026-10-26 04:20:13
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
facebook-verification-system5.blogspot.com: fake profile deletion claim
ai_description
PhishDestroy records facebook-verification-system5.blogspot.com, a page claiming Facebook is deleting unverified profiles.
ai_summary
The captured page at facebook-verification-system5.blogspot.com carries the title "facebook deleting all fake profiles" and a meta description urging readers to verify their location before their account is removed, adding that one account was already verified. The visible screenshot shows only a German Google cookie consent banner with "WEITERE INFORMATIONEN" and "OK" buttons over an otherwise empty page, so the verification interaction described in the metadata is not visible in this capture. The stored VirusTotal result reports 19 detections out of 92 engines.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 03:31:11
revision
90a6e9cf525c230942f96d5131ffa2dc25687dd6bac1d87f9f8664dc3491b519
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: 22 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

Web archive observations

Last observation
First observation
Recorded changes
8
Archived days
9
Snapshots per day
0
Average page size, bytes
2871

Crawler rules

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

Page title and metadata

Page title
Facebook
Open Graph type
movie
Open Graph image
http://i.imgur.com/UKVA9.jpg
Open Graph title
CLICK HERE TO VERIFY YOUR FACEBOOK
Open Graph description
OOOOMMMGGG...Facebook deleting all profiles that are not verifying their location.my account is verified successfully :) verify yours soon friends!!

Trackers

Requests
17
Observed services
  • Name
    Google
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    2
  • Name
    Facebook CDN
    Company
    Meta
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2
  • Name
    blogspot.com
    Company
    Google
    Country
    US
    Category
    Misc
    Requests
    12
  • Name
    Google+ Platform
    Company
    Google
    Country
    US
    Category
    Social Media
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://apis.google.com/js/platform.js
  • https://www.blogger.com/static/v1/common/js/1436446111-csitail.js
Passive insecure
  • http://static.ak.fbcdn.net/rsrc.php/yi/r/q9U99v3_saj.ico
Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
20
Waiting
154
Connection
6
Download
1
Response time, ms
183

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
7716
CO₂, grams
0.0003
Cleaner than, %
77

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.32.10
    Host
    ns1.google.com
  • IP address
    216.239.36.10
    Host
    ns3.google.com
DNS zone
blogspot.com

Location

IP address
2a00:1450:4001:c25::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.14.132
AAAA
  • 2a00:1450:4001:c25::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:c25::84
IP version
6

Redirects

Redirect chain
  • https://facebook-verification-system5.blogspot.com

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
}
Web archive observations
{
    "last": "2026-10-26T00:31:38Z",
    "first": "2013-12-25T19:44:35Z",
    "changes": 8,
    "days_archived": 9,
    "scans_per_day": 0,
    "avg_page_bytes": 2871
}
Crawler rules
{
    "agents": [
        "Mediapartners-Google",
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://facebook-verification-system5.blogspot.com/sitemap.xml"
    ]
}
Page title and metadata
{
    "title": "Facebook",
    "ogType": "movie",
    "ogImage": "http://i.imgur.com/UKVA9.jpg",
    "ogTitle": "CLICK HERE TO VERIFY YOUR FACEBOOK",
    "ogDescription": "OOOOMMMGGG...Facebook deleting all profiles that are not verifying their location.my account is verified successfully :) verify yours soon friends!!"
}
Trackers
{
    "requests": 17,
    "trackers": [
        {
            "name": "Google",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 2
        },
        {
            "name": "Facebook CDN",
            "company": "Meta",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google APIs",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "blogspot.com",
            "company": "Google",
            "country": "US",
            "category": "Misc",
            "requests": 12
        },
        {
            "name": "Google+ Platform",
            "company": "Google",
            "country": "US",
            "category": "Social Media",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://apis.google.com/js/platform.js",
        "https://www.blogger.com/static/v1/common/js/1436446111-csitail.js"
    ],
    "passive_insecure": [
        "http://static.ak.fbcdn.net/rsrc.php/yi/r/q9U99v3_saj.ico"
    ],
    "third_party_scripts": 2
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 20,
        "wait": 154,
        "connect": 6,
        "download": 1
    },
    "response_ms": 183
}
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": 7716,
    "co2_grams": 0.0003,
    "cleaner_than": 77
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.34.10",
            "host": "ns2.google.com"
        },
        {
            "ip": "216.239.38.10",
            "host": "ns4.google.com"
        },
        {
            "ip": "216.239.32.10",
            "host": "ns1.google.com"
        },
        {
            "ip": "216.239.36.10",
            "host": "ns3.google.com"
        }
    ],
    "zone": "blogspot.com"
}
Location
{
    "ip": "2a00:1450:4001:c25::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.14.132"
    ],
    "AAAA": [
        "2a00:1450:4001:c25::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:c25::84",
    "family": 6
}
Redirects
{
    "chain": [
        "https://facebook-verification-system5.blogspot.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "GSE",
        "content-type": "text/html; charset=UTF-8",
        "x-content-type-options": "nosniff"
    }
}

Questions about facebook-verification-system5.blogspot.com

Is facebook-verification-system5.blogspot.com legit?

PhishDestroy records facebook-verification-system5.blogspot.com, a page claiming Facebook is deleting unverified profiles.

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

This report does not record which wallet requests facebook-verification-system5.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 facebook-verification-system5.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 · 8 captures

URLScan · 2026-10-05 1 / 8 Used in the analysis Source file SHA-256: 0cbd3def0612f63fe57cc56646ecab1ede3d69c6e2d00e2918acafe8c34669e3 SHA-256 of the prepared copy given to the model: 6a6c2c3b6499fe9a2e2f7e2e31720c6f947ebc6dc6302704c1aba44ac274cf52
SourceURLScan · 2026-10-05
Recorded
StateStored capture
Final URLhttps://facebook-verification-system5.blogspot.com/
Position1 / 8
Open capture Source Report Wayback Download
All capture links and hashes (8)
facebook-verification-system5.blogspot.com: Facebook impersonation — Flagged by Phishunt, 19/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card facebook-verification-system5.blogspot.com: Facebook impersonation — Flagged by Phishunt, 19/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 066c83beff3b

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Facebook report ↗
IP Reputation Germany142.251.13.132 abuse score 0/100 13 reports Email SpamPort ScanHacking checked Oct 26, 2026 last reported
Platform provider Google Domains US(US)
Abuse contactabuse@google.com, network-abuse@google.com
Hosting abuse contact abuse@google.com, network-abuse@google.com Google LLC · AS15169
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 68/1001 brand signal
Submitted URLhttp://facebook-verification-system5.blogspot.com/
Favicon Hash
Observed page title
facebook deleting all fake profiles
Automated brand references
Facebook
TLS Certificate
Issued by WE2 · stored validity ends in 50 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany142.251.13.132
Network ASN
AS15169
AS name
GOOGLE - Google LLC, US
Organization
Google LLC
Observed location
GermanyFrankfurt am Main, DE
Server header
GSE

Location describes the IP network.

TLS certificate

Issuer
WE2
Valid from
2026-09-28 18:40:34
Valid until
2026-12-21 18:40:33
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint96af029a35a29461434960b48ba2154af0c39c2d7eb0c4b553a22552f01a76ff
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.13.132rapiddns.io

Latest Classified Outcome 2026-10-31 23:09:04 UTC

The site was serving its pages at the latest check.

Technical details
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-31 23:09:04 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:09:04 UTC last content: 2026-10-31 23:09:04 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

19 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
OpenPhish
SOCRadar
Sophos
URLQuery
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://facebook-verification-system5.blogspot.com/
Facebook
Response
HTTP 200
HTML body
6.0 KB
Compressed
2.4 KB
Links
0 internal · 0 external
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0
Content-Encoding: gzip
Server: GSE
Security headers present
X-Content-Type-OptionsX-XSS-Protection
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: CLICK HERE TO VERIFY YOUR FACEBOOK
Open Graph description: OOOOMMMGGG...Facebook deleting all profiles that are not verifying their location.my account is verified successfully :) verify yours soon friends!!
Saved response-header values · 11
Cache-Control
private, max-age=0
Content-Encoding
gzip
Content-Length
2459
Content-Type
text/html; charset=UTF-8
Date
Mon, 26 Oct 2026 00:31:41 GMT
Etag
W/"3f191de5d7e41a5759741c7f3c3582e0e49e4b3733632c23276ac84a5ef63db8"
Expires
Mon, 26 Oct 2026 00:31:41 GMT
Last-Modified
Sun, 01 Sep 2024 00:52:49 GMT
Server
GSE
X-Content-Type-Options
nosniff
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

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

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-10-29 01:56 UTC.

Open this scan on URLScan 01a175a8-37c5-77d0-969c-9584cc2e81dc ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
facebook deleting all fake profiles
Crawler
Facebook
facebook-verification-system5.blogspot.com
Stored observation history5

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Domain monitor · First collection record

    Reachable

All retained availability observations27

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_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:09:04.000000
    Evidence SHA-256
    25cc75d9906ec316d4fef6daa86eb609c282c283655ec50c7aa4b36061e9699d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:09:04
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:09:04.000000
    Evidence SHA-256
    25cc75d9906ec316d4fef6daa86eb609c282c283655ec50c7aa4b36061e9699d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:09:04
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:46.000000
    Evidence SHA-256
    a443bd0d82c953a9d5231041d76a4227d972b49f60862383a266ccf3c79c6529
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:46
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:46.000000
    Evidence SHA-256
    a443bd0d82c953a9d5231041d76a4227d972b49f60862383a266ccf3c79c6529
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:46
    Evidence reason
    alive_content
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:51.000000
    Evidence SHA-256
    eb9b2919b10931978f857512f0000e7a03393ece3c8accefae693bd2149dbc10
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:51
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:51.000000
    Evidence SHA-256
    eb9b2919b10931978f857512f0000e7a03393ece3c8accefae693bd2149dbc10
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:51
    Evidence reason
    alive_content
  8. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:07:12.000000
    Evidence SHA-256
    7a564f92303846e72823f47c32ee526a5b1b4fb5edad82bf79f56a32ebe29cc0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:07:12
    Evidence reason
    alive_content
  9. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:07:12.000000
    Evidence SHA-256
    7a564f92303846e72823f47c32ee526a5b1b4fb5edad82bf79f56a32ebe29cc0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:07:12
    Evidence reason
    alive_content
  10. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:25.000000
    Evidence SHA-256
    d970a3668d71f2aec5e184fa13e9fa294ab9c929f582097956c4191d31c60b1e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:25
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:25.000000
    Evidence SHA-256
    d970a3668d71f2aec5e184fa13e9fa294ab9c929f582097956c4191d31c60b1e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:25
    Evidence reason
    alive_content
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:51.000000
    Evidence SHA-256
    b095cd4e789aefabf1f40cebcaa746f3b6c299f3f14bf6e46605dcd916881037
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:51
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:51.000000
    Evidence SHA-256
    b095cd4e789aefabf1f40cebcaa746f3b6c299f3f14bf6e46605dcd916881037
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:51
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:36:44.000000
    Evidence SHA-256
    084c7410f4b7cbd21970f2d37d6bba11e415c371d5313988d77dd242f2656302
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:36:44
    Evidence reason
    alive_content
  16. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:36:44.000000
    Evidence SHA-256
    084c7410f4b7cbd21970f2d37d6bba11e415c371d5313988d77dd242f2656302
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:36:44
    Evidence reason
    alive_content
  17. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-28 17:03:14.895165
    Evidence SHA-256
    73d1f345e73e3fe3ec20cf30f9fc86221ba9885e7af8cdcc18189657c73b0d4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
    Evidence reason
  18. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:02:48.000000
    Evidence SHA-256
    dd602285c8c940a2575121aaa91580f11aa9047a0f25b91643bcb891da595199
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:02:48
    Evidence reason
    alive_content
  19. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:02:48.000000
    Evidence SHA-256
    dd602285c8c940a2575121aaa91580f11aa9047a0f25b91643bcb891da595199
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:02:48
    Evidence reason
    alive_content
  20. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:03:29.000000
    Evidence SHA-256
    03877a955434d63448ac8d63fdd0c827f5534c52b1639770b8076e310d054855
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:03:29
    Evidence reason
    alive_content
  21. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:03:29.000000
    Evidence SHA-256
    03877a955434d63448ac8d63fdd0c827f5534c52b1639770b8076e310d054855
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:03:29
    Evidence reason
    alive_content
  22. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:03:34.000000
    Evidence SHA-256
    3d684b15ba6560e14cf8b9aa86aafc353cfe53e8b831ed7cd2980991b11fb1cb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:03:34
    Evidence reason
    alive_content
  23. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:03:34.000000
    Evidence SHA-256
    3d684b15ba6560e14cf8b9aa86aafc353cfe53e8b831ed7cd2980991b11fb1cb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:03:34
    Evidence reason
    alive_content
  24. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:40.000000
    Evidence SHA-256
    9b6a23ffb5e0aaab5de4839d6ead09409d117017e4be18a8256006ed16872100
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:40
    Evidence reason
    alive_content
  25. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:40.000000
    Evidence SHA-256
    9b6a23ffb5e0aaab5de4839d6ead09409d117017e4be18a8256006ed16872100
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:40
    Evidence reason
    alive_content
  26. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:44:02.000000
    Evidence SHA-256
    f16e0822a2afe50761dd0cd754718639bd2cef0f36c46035f1397778857b8a86
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:44:02
    Evidence reason
  27. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:44:02.000000
    Evidence SHA-256
    f16e0822a2afe50761dd0cd754718639bd2cef0f36c46035f1397778857b8a86
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:44:02
    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
    facebook-verification-system5.blogspot.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · 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
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 19/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. Added to PhishDestroy

    facebook-verification-system5.blogspot.com

    View source
  2. URLScan

    Page captured

    View source
  3. Wayback Machine

    Page archived

    View source
  4. VirusTotal

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

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 19 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch 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 facebook-verification-system5.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/facebook-verification-system5.blogspot.com"
  title="PhishDestroy threat report for facebook-verification-system5.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>