Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 4. 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
verification-status-confirmed.vercel.app favicon

verification-status-confirmed.vercel.app

In short

PhishDestroy records verification-status-confirmed.vercel.app, a page titled Meta | Privacy Center with a sidebar and privacy content.

“Meta | Privacy Center”

Review the evidence
Registrar
United StatesVercel
Resolved IP
United States216.198.79.195Amazon.com, Inc. · CDN
First observed
Oct 31, 2026
PhishDestroy assessment Critical
72/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 4/92 Stored blocklist matches: 1
VirusTotal
4 / 92
engine detections ·
Blocklist matches
1
PhishFeed
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
10
open gallery
Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records verification-status-confirmed.vercel.app, a page titled Meta | Privacy Center with a sidebar and privacy content.

Critical
Status
Last known active
VirusTotal
4 / 92
Blocklist matches
1
Hosting
United States216.198.79.195Amazon.com, Inc. · CDN
Registrar
United StatesVercel
Page captures
10
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page presents itself as Meta's Privacy Center, with a sidebar offering sections such as Privacy Center, Search, Privacy Policy, Other Terms and Policies, and Settings. The main column repeats the Privacy Center heading, explains privacy choices across Facebook, Instagram, Messenger and other Meta products, and groups content into cards for messaging, privacy, activity settings, and privacy rights. A loading spinner sits over the settings illustration, indicating the page was still rendering when captured.

The stored VirusTotal domain result reports 4 detections out of 92 engines. DNS8 reported "phishing"; SOCRadar reported "suspicious".

Source evidenceVirusTotal 4 / 92 7 sources

VirusTotal

4 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
0
Malicious
3
Suspicious
1
Undetected
88

Vendor labels

DNS8
phishing
SOCRadar
suspicious
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

Tucows Domains Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    216.198.79.3
  • TTL, seconds
    300
    Type
    A
    Value
    64.29.17.3

DNS records observed

JARM fingerprint

3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb

Certificate

Subject alternative names
  • *.vercel.app
  • vercel.app
Issuer
Google Trust Services / WR1
Serial
35b979961bcf79230e4f543f4d6171a3
SHA-256
383fd8fc57a290858bcb55c1a64e783f6d8d76ada331acbe73c36d9966c1f25c
Subject
*.vercel.app
Valid until
Valid from

Registration record

Registrar
Tucows Domains Inc
Registrar IANA ID
69
Registrar URL
http://www.tucows.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.vercel-dns-3.com
  • ns2.vercel-dns-3.com
  • ns3.vercel-dns-3.com
  • ns4.vercel-dns-3.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 0,
    "malicious": 3,
    "suspicious": 1,
    "undetected": 88
}
Vendor labels
{
    "DNS8": "phishing",
    "SOCRadar": "suspicious",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Tucows Domains Inc
Created
2020-01-28T03:03:04Z
Expires
2026-01-28T03:03:04Z
Updated
2025-01-26T03:25:55Z
First seen
2026-10-29T12:08:09Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.3"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.3"
    }
]
Dns at
2026-10-30T12:16:54Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.vercel.app",
        "vercel.app"
    ],
    "issuer": "Google Trust Services / WR1",
    "serial": "35b979961bcf79230e4f543f4d6171a3",
    "sha256": "383fd8fc57a290858bcb55c1a64e783f6d8d76ada331acbe73c36d9966c1f25c",
    "subject": "*.vercel.app",
    "valid_to": "2027-01-27T13:39:48Z",
    "valid_from": "2026-10-29T13:39:49Z"
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "registrar_iana_id": "69",
    "registrar_url": "http://www.tucows.com",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2025-01-26T03:25:55Z",
    "expires": "2026-01-28T03:03:04Z",
    "status": [
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 3 malicious + 1 suspicious / 92 · 2026-10-30 12:16:35 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-30T12:16:35Z
fetched_at
2026-10-31T21:58:27Z
stats
{"timeout":0,"harmless":0,"malicious":3,"suspicious":1,"undetected":88}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Report ID

87780ca1-22bb-477f-8dfd-5a9f9f514db2

Final URL

https://verification-status-confirmed.vercel.app/

HTTP response

200

Navigation history

  • URL
    https://verification-status-confirmed.vercel.app/
    Status
    200

DOM structure hash

ccedd6c319f6407fec82136c3f4ad1f912c8ce2239fb9987c7768785d15a2d0a

Document hash

9dd34f6bcca165ed6d6839a19ca805232616b34b13a8ec50f29f7ca929977d10

Phishing classifier result

  • phishing

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    verification-status-confirmed.vercel.app
    Type
    A
    Value
    64.29.17.131
  • Name
    verification-status-confirmed.vercel.app
    Type
    A
    Value
    216.198.79.131

DNSSEC valid

No

IP address

127.0.1.1

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

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Tucows Domains Inc
Registered
Updated
Expires
Nameservers
  • ns1.vercel-dns-3.com
  • ns2.vercel-dns-3.com
  • ns3.vercel-dns-3.com
  • ns4.vercel-dns-3.com
Original source fields · JSON
Uuid
87780ca1-22bb-477f-8dfd-5a9f9f514db2
Final url
https://verification-status-confirmed.vercel.app/
Status
200
History
[
    {
        "url": "https://verification-status-confirmed.vercel.app/",
        "status": 200
    }
]
DOM structure hash
ccedd6c319f6407fec82136c3f4ad1f912c8ce2239fb9987c7768785d15a2d0a
Document hash
9dd34f6bcca165ed6d6839a19ca805232616b34b13a8ec50f29f7ca929977d10
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "verification-status-confirmed.vercel.app",
        "type": "A",
        "value": "64.29.17.131"
    },
    {
        "name": "verification-status-confirmed.vercel.app",
        "type": "A",
        "value": "216.198.79.131"
    }
]
Dnssec valid
false
Ip
127.0.1.1

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

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2026-03-14T03:03:04Z",
    "expires": "2036-01-28T03:03:04Z",
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

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

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

URLScan

Malicious

SHA-256 167ad23af57ef73d6453bbf040586b3cd7dcd92c5a1c6b1a78a9bf16a57bb5df

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a193fc-bc23-77e3-8c02-9ec375bd105c

Final URL

https://verification-status-confirmed.vercel.app/privacy-centers.html

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://verification-status-confirmed.vercel.app/privacy-centers.html
    From
    http://verification-status-confirmed.vercel.app/privacy-centers.html
    Status
    307

IP address

64.29.17.131

Contacted domains

  • www.gstatic.com
  • cdn.tailwindcss.com
  • translate-pa.googleapis.com
  • www.google.com
  • fonts.gstatic.com
  • ipinfo.io
  • translate.googleapis.com
  • translate.google.com
  • cdnjs.cloudflare.com

Contacted IP addresses

  • 172.217.115.4
  • 142.251.157.119
  • 142.251.16.94
  • 34.117.59.81
  • 142.251.210.42
  • 142.251.45.195
  • 142.250.217.14
  • 104.17.24.14
  • 104.26.3.143
  • 64.29.17.131

Autonomous systems (ASN)

  • 15169
  • 396982
  • 13335
  • 16509

Server countries

  • US

Document hash

167ad23af57ef73d6453bbf040586b3cd7dcd92c5a1c6b1a78a9bf16a57bb5df

Script hashes

  • 3cbd370a6cb0a6a588b02b21a6e566825249a7faab144893c253cdae33053bab
  • be894e782d4ff2dd651d9b9aa249de18578c9cca1ee7eb853583cd5a1215a34a
  • 210bb6d77c9d6c54cbc3c96ce3aa22975ff6a169dc4f4736510e1ca9e1910916
  • 35c9650f88a6c357fe168ef2144eaf073b84cad46b48b97c3c762a6b61726609
  • 80a76afdf19c68c06a125530ddab599a16d6fd6bf410582ef1fe8e0487af2d45

JavaScript globals

  • tailwind
  • CryptoJS
  • googleTranslateElementInit
  • _DumpException
  • google
  • /template.html
  • openClientModal
  • openSecurityModal
  • openAuthenticationModal
  • openSuccessModal
  • default_tr
  • _F_toggles_default_tr
  • closure_lm_956599
  • CONFIG
  • Utils
  • Modal

TLS session and certificate

Subject alternative names
  • *.vercel.app
Cipher
AES_128_GCM
Issuer
WR1
Subject
*.vercel.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

2

Registered domain age, days

2468

Certificate age, days

0

Certificate validity, days

89

Page requests

20

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
100
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • meta
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Meta
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a193fc-bc23-77e3-8c02-9ec375bd105c
Final url
https://verification-status-confirmed.vercel.app/privacy-centers.html
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://verification-status-confirmed.vercel.app/privacy-centers.html",
        "from": "http://verification-status-confirmed.vercel.app/privacy-centers.html",
        "status": 307
    }
]
Ip
64.29.17.131
Contacted domains
[
    "www.gstatic.com",
    "cdn.tailwindcss.com",
    "translate-pa.googleapis.com",
    "www.google.com",
    "fonts.gstatic.com",
    "ipinfo.io",
    "translate.googleapis.com",
    "translate.google.com",
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "172.217.115.4",
    "142.251.157.119",
    "142.251.16.94",
    "34.117.59.81",
    "142.251.210.42",
    "142.251.45.195",
    "142.250.217.14",
    "104.17.24.14",
    "104.26.3.143",
    "64.29.17.131"
]
Asns
[
    "15169",
    "396982",
    "13335",
    "16509"
]
Countries
[
    "US"
]
Document hash
167ad23af57ef73d6453bbf040586b3cd7dcd92c5a1c6b1a78a9bf16a57bb5df
Script hashes
[
    "3cbd370a6cb0a6a588b02b21a6e566825249a7faab144893c253cdae33053bab",
    "be894e782d4ff2dd651d9b9aa249de18578c9cca1ee7eb853583cd5a1215a34a",
    "210bb6d77c9d6c54cbc3c96ce3aa22975ff6a169dc4f4736510e1ca9e1910916",
    "35c9650f88a6c357fe168ef2144eaf073b84cad46b48b97c3c762a6b61726609",
    "80a76afdf19c68c06a125530ddab599a16d6fd6bf410582ef1fe8e0487af2d45"
]
Globals
[
    "tailwind",
    "CryptoJS",
    "googleTranslateElementInit",
    "_DumpException",
    "google",
    "/template.html",
    "openClientModal",
    "openSecurityModal",
    "openAuthenticationModal",
    "openSuccessModal",
    "default_tr",
    "_F_toggles_default_tr",
    "closure_lm_956599",
    "CONFIG",
    "Utils",
    "Modal"
]
Tls
{
    "san": [
        "*.vercel.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR1",
    "subject": "*.vercel.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-29T11:46:09Z",
    "valid_from": "2026-10-31T11:46:10Z"
}
Domain age days
2
Apex age days
2468
Tls age days
0
Tls valid days
89
Requests
20
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "meta"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Meta"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
}
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
01a190d9-c100-73f8-a6b5-a768c0e7b506
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report

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
verification-status-confirmed.vercel.app — Meta Privacy Center page
ai_description
PhishDestroy records verification-status-confirmed.vercel.app, a page titled Meta | Privacy Center with a sidebar and privacy content.
ai_summary
The captured page presents itself as Meta's Privacy Center, with a sidebar offering sections such as Privacy Center, Search, Privacy Policy, Other Terms and Policies, and Settings. The main column repeats the Privacy Center heading, explains privacy choices across Facebook, Instagram, Messenger and other Meta products, and groups content into cards for messaging, privacy, activity settings, and privacy rights. A loading spinner sits over the settings illustration, indicating the page was still rendering when captured. The stored VirusTotal domain result reports 4 detections out of 92 engines. DNS8 reported "phishing"; SOCRadar reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 22:59:58
revision
31f74016632197db76f556680e7bdfcd2e957791bcdd4f4db733e527ef1c9a05
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: 21 fields

Mail configuration

SPF lookups
0

CAA records

Count
2
Domain
vercel.app
Allowed issuers
  • pki.goog
  • letsencrypt.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
4492

Page title and metadata

Page title
Meta | Privacy Center

Trackers

Requests
24
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    jsDelivr
    Company
    jsDelivr
    Category
    Hosting
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://cdn.tailwindcss.com/
  • https://cdnjs.cloudflare.com/ajax/libs/crypto-js/4.2.0/crypto-js.min.js
Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
16
TLS
23
Waiting
17
Connection
6
Download
0
Response time, ms
62

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

Carbon estimate

Bytes
20251
CO₂, grams
0.0007
Cleaner than, %
56

DNS servers

Nameservers
  • IP address
    205.251.199.60
    Host
    ns4.vercel-dns-3.com
  • IP address
    205.251.193.92
    Host
    ns1.vercel-dns-3.com
  • IP address
    205.251.194.149
    Host
    ns2.vercel-dns-3.com
  • IP address
    205.251.197.116
    Host
    ns3.vercel-dns-3.com
DNS zone
vercel.app

Location

IP address
216.198.79.195
ASN
16509
Organization
Amazon.com, Inc.
City
Walnut
Country
US

TLS certificate

Issuer
Google Trust Services / WR1
Subject
*.vercel.app

DNS records

A
  • 216.198.79.195
  • 64.29.17.195

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

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; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
216.198.79.195
IP version
4

Redirects

Redirect chain
  • https://verification-status-confirmed.vercel.app

HTTP headers

Response headers
Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "vercel.app",
    "issuers": [
        "pki.goog",
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-31T21:58:10Z",
    "first": "2026-10-31T21:58:10Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 4492
}
Page title and metadata
{
    "title": "Meta | Privacy Center"
}
Trackers
{
    "requests": 24,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn.tailwindcss.com/",
        "https://cdnjs.cloudflare.com/ajax/libs/crypto-js/4.2.0/crypto-js.min.js"
    ],
    "third_party_scripts": 2
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 16,
        "tls": 23,
        "wait": 17,
        "connect": 6,
        "download": 0
    },
    "response_ms": 62
}
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
    ]
}
Carbon
{
    "bytes": 20251,
    "co2_grams": 0.0007,
    "cleaner_than": 56
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.199.60",
            "host": "ns4.vercel-dns-3.com"
        },
        {
            "ip": "205.251.193.92",
            "host": "ns1.vercel-dns-3.com"
        },
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        },
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Location
{
    "ip": "216.198.79.195",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Walnut",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "216.198.79.195",
        "64.29.17.195"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "216.198.79.195",
    "family": 4
}
Redirects
{
    "chain": [
        "https://verification-status-confirmed.vercel.app"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}

Questions about verification-status-confirmed.vercel.app

Is verification-status-confirmed.vercel.app legit?

PhishDestroy records verification-status-confirmed.vercel.app, a page titled Meta | Privacy Center with a sidebar and privacy content.

Is verification-status-confirmed.vercel.app safe to connect a wallet?

This report does not record which wallet requests verification-status-confirmed.vercel.app 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 verification-status-confirmed.vercel.app?

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 · PhishFeed · no match in the other 10 2
PhishDestroy PhishDestroy list View source
PhishFeed Listed View source

Checked, no match

Last checked

Stored Capture · 10 captures

Cloudflare Radar 1 / 10 Used in the analysis Source file SHA-256: 796ca2e4c8cb4eeee7d6c4ae727fc1f6d45a78032dc285a53a3aef6241fa6f6c SHA-256 of the prepared copy given to the model: 9b2ef7277e6f2fb6d0b3711b9f858f15d710f5689172206471945f7399b2e50c
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://verification-status-confirmed.vercel.app/
Position1 / 10
Open capture Source Report Wayback Download
All capture links and hashes (10)

Domain details

Domain
IP Context United States216.198.79.195 Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Vercel US(US)
Abuse contactabuse@vercel.com
Hosting abuse contact abuse@vercel.com Amazon.com, Inc. · AS16509
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 10/1001 brand signal
Submitted URLhttp://verification-status-confirmed.vercel.app/privacy-centers.html
Observed page title
Meta | Privacy Center
Automated brand references
Google
TLS Certificate
Issued by Google Trust Services / WR1 · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR1
Valid from
2026-10-29 13:39:49
Valid until
2027-01-27 13:39:48
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint383fd8fc57a290858bcb55c1a64e783f6d8d76ada331acbe73c36d9966c1f25c
Certificate names · 2 SANs
  • *.vercel.app
  • vercel.app

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

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
DNS8
Gridinsoft
SOCRadar

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of verification-status-confirmed.vercel.app · checked Oct 31, 2026

90
Good
Performance
FCP
2.31 s
First Contentful Paint
LCP
3.17 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.87 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 200
Requested URL: http://verification-status-confirmed.vercel.app/privacy-centers.html
Final URL: https://verification-status-confirmed.vercel.app/privacy-centers.html
Meta Verified - Rewards for you
Response
HTTP 200
HTML body
6.7 KB
Compressed
2.5 KB
Links
5 internal · 0 external
Selected response headers
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Vercel
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
Access-Control-Allow-Origin
*
Age
31926
Cache-Control
public, max-age=0, must-revalidate
Content-Disposition
inline; filename="privacy-centers.html"
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 31 Oct 2026 21:58:01 GMT
Etag
W/"f16ddc592b3feaf42f9674c9e7fd3608"
Last-Modified
Sat, 31 Oct 2026 13:05:54 GMT
Server
Vercel
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Transfer-Encoding
chunked
X-Vercel-Cache
HIT
X-Vercel-Id
yul1::4bxgq-1793483881330-efc662cf39d5

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

Archived

Captured network requests

Network requests: 20 SHA-256 hashes: 20 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-31 22:08 UTC.

Open this scan on URLScan 01a193fc-bc23-77e3-8c02-9ec375bd105c ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability 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
    Recorded HTTP status
    200
    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-31 22:59:53.406979
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

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
    verification-status-confirmed.vercel.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 4/92
  • Blocklist Detection
    Found in blocklists: PhishFeed
  • 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

5 entries
  1. URLScan

    Page captured

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    verification-status-confirmed.vercel.app

    View source
  5. VirusTotal

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

Check for cloaking

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

verification-status-confirmed.vercel.app

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 4 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

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

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

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

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