Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
facebook-badge-center.com favicon

facebook-badge-center.com

In short

facebook-badge-center.com is a Facebook impersonation page detected by PhishDestroy on 2026-10-26.

Review the evidence
Registrar
Name.com
Resolved IP
216.198.79.65
Registered
Jun 4, 2026
PhishDestroy assessment Critical
First observed Oct 26, 2026 00:29 UTC · PhishDestroy
Risk signals
VirusTotal detections: 16/92 Automated brand label: Facebook
VirusTotal
16 / 92
engine detections ·
OTX
3
community references
Cloudflare Radar
—
Not recorded
Page captures
4
open gallery
Domain age
143 days
Reports sent
—
No sent record
OTX: 3 refs Oct 26, 2026 CDN
X Telegram API

Analysis

Domain summary

facebook-badge-center.com is a Facebook impersonation page detected by PhishDestroy on 2026-10-26. Risk: critical (95/100). Registrar: Name.com. Hosting: Amazon.com, Inc. VirusTotal: 16/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
16 / 92
OTX
3 community refs
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added facebook-badge-center.com to its internal blocklist on 2026-10-26 after the intake flagged the domain because VirusTotal reported numerous malicious detections. When fetched on 2026-10-26 the site returned HTTP 451, indicating the content was unavailable at that time.

How the scam works

The vendor detections associated with this domain are typical of phishing or fraud campaigns that impersonate trusted brands to harvest credentials, but no specific malicious page content or credential‑collection form was observed in the available scans. Consequently, the listing reflects a general risk category rather than a confirmed on‑page behavior.

Evidence

VirusTotal analysis on 2026-10-21 (retrieved 2026-10-26) recorded 14 malicious and 2 suspicious detections out of 92 engines, with vendors such as BitDefender, ESET and Fortinet flagging the domain as phishing. Google Safe Browsing checked on 2026-10-26 did not flag the domain. URLScan captured the site on 2026-08-14 and reported an overall clean verdict, though its engine scoring marked it malicious with a score of 75. Cloudflare Radar scanned on 2026-10-26 labeled the domain malicious under the malware category, and OTX listed three pulses referencing it as of the same date. PhishDestroy’s internal blocklist marks the domain as blocked, while external blocklists showed no entries at the time of checking.

Infrastructure

The domain was registered with Name.com, Inc. on 2026-06-04 and uses Vercel DNS nameservers. Hosting records show IP addresses 216.198.79.65 (Amazon.com, Inc., US) and 64.29.17.1, both serving a TLS certificate from Let’s Encrypt valid from 2026-10-13 to 2027-01-11. The server header reports Vercel, and HSTS is enabled with a max‑age of two years; DNSSEC is not configured.

What to do

Do not enter any credentials, personal information, or download files from this domain; if you have already submitted credentials, change the associated passwords immediately. Security teams should block facebook-badge-center.com at the firewall or DNS level and monitor for any outbound connections to its recorded IPs. Continue to watch vendor feeds for updates, as the domain’s risk rating may evolve.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-26T00:33:14Z)URLScan screenshot (2026-08-07T01:17:06Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 16 / 92 · OTX 3 references 7 sources

VirusTotal

16 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
14
Suspicious
2
Undetected
32

Vendor labels

DNS8
suspicious
ESET
phishing
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Registrar

Name.com, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    A
    Value
    216.198.79.1
  • TTL, seconds
    60
    Type
    CAA
    Value
    sectigo.com
  • TTL, seconds
    60
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.vercel-dns.com
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    hostmaster.nsone.net
    Value
    ns1.vercel-dns.com
  • TTL, seconds
    60
    Type
    CAA
    Value
    pki.goog
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.vercel-dns.com
  • TTL, seconds
    1800
    Type
    A
    Value
    64.29.17.1

DNS records observed

JARM fingerprint

3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb

Certificate

Subject alternative names
  • *.facebook-badge-center.com
  • facebook-badge-center.com
Issuer
Let's Encrypt / YR2
Serial
633065204872b4011b06abe98fd53f7c8d4
SHA-256
93ce482da88524ce437c0f26cc62391980131f3c1b99a626a74d56b886bd3207
Subject
*.facebook-badge-center.com
Valid until
Valid from

Registration record

Registrar
Name.com, Inc.
Registrar IANA ID
625
Registrar URL
http://www.name.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com
DNSSEC
unSigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 14,
    "suspicious": 2,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Registrar
Name.com, Inc.
Created
2026-06-04T10:35:26Z
Expires
2027-06-04T10:35:26Z
Updated
2026-06-04T10:35:26Z
First seen
2026-06-04T11:26:01Z
DNS records
[
    {
        "ttl": 1800,
        "type": "A",
        "value": "216.198.79.1"
    },
    {
        "ttl": 60,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 60,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.vercel-dns.com"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "hostmaster.nsone.net",
        "value": "ns1.vercel-dns.com"
    },
    {
        "ttl": 60,
        "type": "CAA",
        "value": "pki.goog"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.vercel-dns.com"
    },
    {
        "ttl": 1800,
        "type": "A",
        "value": "64.29.17.1"
    }
]
Dns at
2026-10-21T08:04:01Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.facebook-badge-center.com",
        "facebook-badge-center.com"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "633065204872b4011b06abe98fd53f7c8d4",
    "sha256": "93ce482da88524ce437c0f26cc62391980131f3c1b99a626a74d56b886bd3207",
    "subject": "*.facebook-badge-center.com",
    "valid_to": "2027-01-11T05:03:43Z",
    "valid_from": "2026-10-13T05:03:44Z"
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "registrar_iana_id": "625",
    "registrar_url": "http://www.name.com",
    "created": "2026-06-04T10:35:26Z",
    "updated": "2026-06-04T10:35:26Z",
    "expires": "2027-06-04T10:35:26Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.vercel-dns.com",
        "ns2.vercel-dns.com"
    ],
    "dnssec": "unSigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-06-04T10:35:26Z",
        "last changed": "2026-06-04T10:35:26Z",
        "registration": "2026-06-04T10:35:26Z",
        "registrar expiration": "2027-06-04T10:35:26Z",
        "last update of RDAP database": "2026-06-04T10:35:26Z"
    }
}
Separate source record · 14 malicious + 2 suspicious / 92 · 2026-10-21 07:58:32 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-21T07:58:32Z
fetched_at
2026-10-26T01:02:23Z
stats
{"timeout":0,"harmless":44,"malicious":14,"suspicious":2,"undetected":32}

URLScan

Malicious · engine verdict · score 75

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

019ffe64-e04e-741a-8375-4d8350c7975d

Final URL

https://facebook-badge-center.com/live

HTTP response

451

IP address

64.29.17.1

Contacted IP addresses

  • 64.29.17.1

Autonomous systems (ASN)

  • 16509

Server countries

  • US

Document hash

af5db186ec8654f5924f49c5713d54b37761bbe983136417c1634cf13f9e401d

JavaScript globals

  • fence

TLS session and certificate

Subject alternative names
  • facebook-badge-center.com
Cipher
AES_128_GCM
Issuer
YR2
Subject
facebook-badge-center.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

70

Registered domain age, days

70

Certificate age, days

8

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
75
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000
Original source fields · JSON
Uuid
019ffe64-e04e-741a-8375-4d8350c7975d
Final url
https://facebook-badge-center.com/live
Status
451
Ip
64.29.17.1
Contacted IP addresses
[
    "64.29.17.1"
]
Asns
[
    "16509"
]
Countries
[
    "US"
]
Document hash
af5db186ec8654f5924f49c5713d54b37761bbe983136417c1634cf13f9e401d
Globals
[
    "fence"
]
Tls
{
    "san": [
        "facebook-badge-center.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "facebook-badge-center.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-04T02:14:14Z",
    "valid_from": "2026-08-06T02:14:15Z"
}
Domain age days
70
Apex age days
70
Tls age days
8
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 75,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000"
}
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
019ffe64-e04e-741a-8375-4d8350c7975d
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

3 community references

Open report

Cloudflare Radar

Scan report

Not recorded
Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

4b700100-40f7-4988-9665-6635aa7af726

Final URL

https://facebook-badge-center.com/

HTTP response

451

Navigation history

  • URL
    https://facebook-badge-center.com/
    Status
    451

DOM structure hash

43cc15c7d4b1578d88aa62258b07172404f09ae234cba63ccd261df8ad1ec377

Document hash

7b5868555c6adadc65129e18cb895e4d806d71b5c838cb6261f650c2d120a2b9

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    facebook-badge-center.com
    Type
    A
    Value
    64.29.17.65
  • Name
    facebook-badge-center.com
    Type
    A
    Value
    64.29.17.1

DNSSEC valid

No

IP address

64.29.17.65

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
Name.com, Inc.
Registered
Updated
Expires
Nameservers
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com
Original source fields · JSON
Uuid
4b700100-40f7-4988-9665-6635aa7af726
Final url
https://facebook-badge-center.com/
Status
451
History
[
    {
        "url": "https://facebook-badge-center.com/",
        "status": 451
    }
]
DOM structure hash
43cc15c7d4b1578d88aa62258b07172404f09ae234cba63ccd261df8ad1ec377
Document hash
7b5868555c6adadc65129e18cb895e4d806d71b5c838cb6261f650c2d120a2b9
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "facebook-badge-center.com",
        "type": "A",
        "value": "64.29.17.65"
    },
    {
        "name": "facebook-badge-center.com",
        "type": "A",
        "value": "64.29.17.1"
    }
]
Dnssec valid
false
Ip
64.29.17.65
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "created": "2026-06-04T10:35:26Z",
    "updated": "2026-06-04T10:35:26Z",
    "expires": "2027-06-04T10:35:26Z",
    "nameservers": [
        "ns1.vercel-dns.com",
        "ns2.vercel-dns.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-26T01:04:02Z

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
0
analyzed_at
2026-10-26T01:04:02Z
source_timestamp
2026-10-26 02:04:02
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-badge-center.com — Suspicious Domain
ai_description
PhishDestroy flags facebook-badge-center.com as a suspicious domain after multiple security vendor detections; visitors should treat the site with caution.
ai_generated_at
2026-10-26T01:03:50Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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: 15 fields

Mail configuration

SPF lookups
0

CAA records

Count
3
Domain
facebook-badge-center.com
Allowed issuers
  • letsencrypt.org
  • pki.goog
  • sectigo.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

TLS connection

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

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    198.51.45.13
    Host
    ns2.vercel-dns.com
  • IP address
    198.51.44.13
    Host
    ns1.vercel-dns.com
DNS zone
facebook-badge-center.com

Location

IP address
216.198.79.1
ASN
16509
Organization
Amazon.com, Inc.
Country
US

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
*.facebook-badge-center.com

DNS records

A
  • 64.29.17.1
  • 216.198.79.1
NS
  • ns2.vercel-dns.com
  • ns1.vercel-dns.com
SOA
Primary nameserver
ns1.vercel-dns.com
Hostmaster
hostmaster.nsone.net
Serial
1780569328
Refresh, seconds
43200
Retry, seconds
7200
Expiry, seconds
1209600
Minimum TTL, seconds
600

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000
Observation
HSTS header does not include all subdomains.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=63072000
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
64.29.17.1
IP version
4

Registration record

Registrar
Name.com, Inc.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

HTTP headers

Response headers
Server
Vercel
Content-type
text/plain; charset=utf-8
Strict-transport-security
max-age=63072000
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 3,
    "domain": "facebook-badge-center.com",
    "issuers": [
        "letsencrypt.org",
        "pki.goog",
        "sectigo.com"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.45.13",
            "host": "ns2.vercel-dns.com"
        },
        {
            "ip": "198.51.44.13",
            "host": "ns1.vercel-dns.com"
        }
    ],
    "zone": "facebook-badge-center.com"
}
Location
{
    "ip": "216.198.79.1",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "*.facebook-badge-center.com"
}
DNS records
{
    "A": [
        "64.29.17.1",
        "216.198.79.1"
    ],
    "NS": [
        "ns2.vercel-dns.com",
        "ns1.vercel-dns.com"
    ],
    "SOA": "{\"nsname\": \"ns1.vercel-dns.com\", \"hostmaster\": \"hostmaster.nsone.net\", \"serial\": 1780569328, \"refresh\": 43200, \"retry\": 7200, \"expire\": 1209600, \"minttl\": 600}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "64.29.17.1",
    "family": 4
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "created": "2026-06-04T10:35:26Z",
    "updated": "2026-06-04T10:35:26Z",
    "expires": "2027-06-04T10:35:26Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.vercel-dns.com",
        "ns2.vercel-dns.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/plain; charset=utf-8",
        "strict-transport-security": "max-age=63072000"
    }
}

Questions about facebook-badge-center.com

Is facebook-badge-center.com legit?

No. PhishDestroy classifies facebook-badge-center.com as a Facebook impersonation page (risk: critical, 95/100); it was first detected on 2026-10-26. VirusTotal: 16/92 engines flag it. Treat the site as unsafe.

Is facebook-badge-center.com safe to connect a wallet?

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

What should I do if I used facebook-badge-center.com?

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

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded
StateStored capture
HTTP status451
Final URLhttps://facebook-badge-center.com/live
Position1 / 4
Open capture Wayback Download
All capture links and hashes (4)

Domain details

Domain
IP Context Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Name.com SE(SE)
Abuse contact["abuse@name.com", "fe5f44beb6fda8ces@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for facebook-badge-center.com →
Hosting abuse contact abuse@name.com Amazon.com, Inc. · AS16509
RegistrationCreated Jun 4, 2026 (143d) — Expires Jun 4, 2027
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 0/100
Submitted URLhttp://facebook-badge-center.com/
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 77 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.198.79.65
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-13 05:03:44
Valid until
2027-01-11 05:03:43
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint93ce482da88524ce437c0f26cc62391980131f3c1b99a626a74d56b886bd3207
Certificate names · 2 SANs
  • *.facebook-badge-center.com
  • facebook-badge-center.com

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

viewdns.info · 216.198.79.65rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of facebook-badge-center.com · checked Oct 26, 2026

100
Good
Performance
FCP
0.79 s
First Contentful Paint
LCP
0.79 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.79 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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 451
Requested URL: http://facebook-badge-center.com/
Final URL: https://facebook-badge-center.com/
Deployment Unavailable
Response
HTTP 451
HTML body
1.6 KB
Compressed
831 B
Links
0 internal · 0 external
Selected response headers
Cache-Control: public, max-age=0, must-revalidate
Content-Type: text/html; charset=utf-8
Server: Vercel
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 8
Cache-Control
public, max-age=0, must-revalidate
Content-Length
1590
Content-Type
text/html; charset=utf-8
Date
Mon, 26 Oct 2026 00:30:27 GMT
Server
Vercel
Strict-Transport-Security
max-age=63072000
X-Vercel-Error
DEPLOYMENT_DISABLED
X-Vercel-Id
fra1::nzd4b-1792974627875-a36db68c67eb

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

Archived
All retained availability observations1

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
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:37:38.990077
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Recorded activity

4 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    16/92 engine detections

    View source
  3. Added to PhishDestroy

    facebook-badge-center.com

    View source
  4. URLScan

    Malicious · engine verdict · score 75

    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

Check for cloaking

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

facebook-badge-center.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 16 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 3 refs 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?

4 evidence signal groups linked Unverified
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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

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

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.

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

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including facebook-badge-center.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-badge-center.com"
  title="PhishDestroy threat report for facebook-badge-center.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>