Skip to security report
Domain security and threat intelligence
verication-casefb368-pink.vercel.app favicon

verication-casefb368-pink.vercel.app

In short

verication-casefb368-pink.vercel.app is a Meta impersonation page detected by PhishDestroy on 2026-10-23. Risk: critical (95/100). Registrar: Vercel. Status: Content unavailable. Hosting: Amazon.com, Inc. VirusTotal: 17/92 engines flag it. Do not enter credentials or connect a wallet.

“Meta Verified - Rewards for you”

Registrar
Vercel
Resolved IP
64.29.17.3
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 17/92 Automated brand label: Meta
VirusTotal
engine detections
OTX
community references
Cloudflare Radar
source verdict
Page captures
open gallery
Domain age
Not recorded
Reports sent
No sent record
Oct 23, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 17. Exercise extreme caution — do not enter credentials or personal information.
Source evidenceVirusTotal 17 / 92 5 sources

VirusTotal

17 / 92 engine detections

Open report
VirusTotal · 2026-10-23T00:34:47Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 0,
    "malicious": 0,
    "suspicious": 1,
    "undetected": 91
}
Vendor labels
{
    "DNS8": "suspicious"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Google": "technology",
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "Forcepoint ThreatSeeker": "information technology"
}
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-22T16:15:09Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.3"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.3"
    }
]
Dns at
2026-10-23T00:40:29Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.vercel.app"
    ],
    "issuer": "Google Trust Services / WR1",
    "serial": "f7911168ffa7d0f4135e24792e7a52a8",
    "sha256": "8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093",
    "subject": "*.vercel.app",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
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"
}

Cloudflare Radar

Malicious

Not recorded
Open report
Cloudflare Radar · 2026-10-23T21:05:49Z

Observed: · Retrieved:

Uuid
2d802a0e-3c15-400e-83ed-d166d586af87
Final url
https://verication-casefb368-pink.vercel.app/
Status
200
History
[
    {
        "url": "https://verication-casefb368-pink.vercel.app/",
        "status": 200
    }
]
DOM structure hash
ccedd6c319f6407fec82136c3f4ad1f912c8ce2239fb9987c7768785d15a2d0a
Document hash
502cb4a612dbacbe798c9f955b4850f830323c7457cb631f80c1bb28cc262b37
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "verication-casefb368-pink.vercel.app",
        "type": "A",
        "value": "216.198.79.195"
    },
    {
        "name": "verication-casefb368-pink.vercel.app",
        "type": "A",
        "value": "64.29.17.195"
    }
]
Dnssec valid
false
Ip
216.198.79.195
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"
    ]
}

URLScan

Malicious

Open report
URLScan · 2026-10-23T02:29:07Z

Observed: · Retrieved:

Uuid
01a16697-1ed6-702b-852d-bcb1b4f33f8a
Final url
https://verication-casefb368-pink.vercel.app/privacy-centers.html
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://verication-casefb368-pink.vercel.app/privacy-centers.html",
        "from": "http://verication-casefb368-pink.vercel.app/privacy-centers.html",
        "status": 307
    }
]
Ip
216.198.79.3
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.151.119",
    "34.117.59.81",
    "142.251.14.95",
    "142.251.20.94",
    "142.251.20.100",
    "104.17.24.14",
    "104.26.3.143",
    "216.198.79.3"
]
Asns
[
    "15169",
    "396982",
    "13335",
    "16509"
]
Countries
[
    "US"
]
Document hash
a94cc5b20eeaa208c5ddf912f11021df07e07551393ddeb1ea34f48321df9a02
Script hashes
[
    "df0b8bdda623876921ec12fa8412e85c456f567f36858de216ba5ef8b549f036",
    "3b95aa145f966d8e927ad964b3dc1e5f5bb2532e92606541e206eaf60cc9fd47",
    "c6e76378422c0c5b4da01396be2ff54ad64d124db891e875df4ad77f1d24c098",
    "659f200aa99e9d1c6a899ad4cb3452295c62045487fb78426aacd2c689ec82c5",
    "733edf43d8608eb0097522529efc8f18c7aed2eee5613d2a015d693d2bccf95e"
]
Globals
[
    "tailwind",
    "CryptoJS",
    "googleTranslateElementInit",
    "_DumpException",
    "google",
    "/template.html",
    "openClientModal",
    "openSecurityModal",
    "openAuthenticationModal",
    "openSuccessModal",
    "default_tr",
    "_F_toggles_default_tr",
    "closure_lm_699677",
    "CONFIG",
    "Utils",
    "Modal"
]
Tls
{
    "san": [
        "*.vercel.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR1",
    "subject": "*.vercel.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Domain age days
0
Apex age days
0
Tls age days
54
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"
}

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

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 checks · 2026-10-23T07:04:30Z
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-23T01:53:14Z",
    "first": "2026-10-23T01:53:14Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 4520
}
Page title and metadata
{
    "title": "Meta | Privacy Center"
}
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": 26,
        "tls": 10,
        "wait": 26,
        "connect": 7,
        "download": 1
    },
    "response_ms": 70
}
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": 20629,
    "co2_grams": 0.0008,
    "cleaner_than": 56
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        },
        {
            "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"
        }
    ],
    "zone": "vercel.app"
}
Location
{
    "ip": "64.29.17.195",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "64.29.17.195",
        "216.198.79.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://verication-casefb368-pink.vercel.app"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Questions about verication-casefb368-pink.vercel.app

Is verication-casefb368-pink.vercel.app legit?

No. PhishDestroy classifies verication-casefb368-pink.vercel.app as a Meta impersonation page (risk: critical, 95/100); it was first detected on 2026-10-23. VirusTotal: 17/92 engines flag it. Treat the site as unsafe.

Is verication-casefb368-pink.vercel.app safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on verication-casefb368-pink.vercel.app. 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 verication-casefb368-pink.vercel.app?

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 · 9 captures

All capture links and hashes (9)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Meta report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Vercel US(US)
Abuse contactabuse@vercel.com
HTTP Status451 Unavailable For Legal Reasons
Time to First Unavailability 32h
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 68/1001 brand signal
Submitted URLhttp://verication-casefb368-pink.vercel.app/privacy-centers.html
Favicon Hash
Observed page title
Meta Verified - Rewards for you
Automated brand references
Google
TLS Certificate
Issued by WR1 · stored validity ends in 33 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WR1
Valid from
2026-08-29 19:48:09
Valid until
2026-11-27 19:48:08
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Certificate names · 1 SAN
  • *.vercel.app

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

Latest Classified Outcome 2026-10-25 02:54:20 UTC

Primary outcome Provider block observed reason: Vercel Deployment Disabled 95% confidence
Attribution Vercel mechanism: Deployment Disabled source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Stale Registration: Unknown
Latest HTTP observation Provider block observed Vercel Deployment Disabled Vercel Deployment Disabled 95% provider marker verified 2026-10-25 02:54:20 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 22:35:13 UTC last content: 2026-10-23 22:35:13 UTC current episode first observed: 2026-10-24 10:32:29 UTC observed RIP window: 2026-10-23 22:35:13 UTC → 2026-10-24 10:32:29 UTC · 11.95h midpoint estimate ≈ 2026-10-24 04:33:51 UTC · precision medium · basis bounded
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.
Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Netcraft
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://verication-casefb368-pink.vercel.app/privacy-centers.html
Final URL: https://verication-casefb368-pink.vercel.app/privacy-centers.html
Meta Verified - Rewards for you
Response
HTTP 200
HTML body
6.8 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
155112
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
Fri, 23 Oct 2026 02:00:46 GMT
Etag
W/"211f972bc4728faf6ef083eafde35594"
Last-Modified
Wed, 21 Oct 2026 06:55:33 GMT
Server
Vercel
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Transfer-Encoding
chunked
X-Vercel-Cache
HIT
X-Vercel-Id
fra1::xnsm4-1792720846211-d716517cca89

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

Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
11.95
Estimate basis
Bounded by observations
Estimate precision
Medium

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

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

    https://radar.cloudflare.com/scan/2d802a0e-3c15-400e-83ed-d166d586af87

  2. Availability monitor · Recorded state

    live_content→blocked

    vercel_deployment_disabled · Vercel · deployment_disabled

  3. Availability monitor · Recorded state

    Reachable→Unavailable

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · First collection record

    Reachable

All retained availability observations5

Source: availability monitor. This journal includes earlier observations and repeated states with distinct dates or evidence. Identical records appear once; an unknown state is not proof that the site is offline.

  1. blocked
    Cause
    vercel_deployment_disabled
    Recorded actor
    Vercel
    Mechanism
    deployment_disabled
    Monitor confidence
    95
    Original source timestamp
    2026-10-25 03:54:20.000000
    Evidence SHA-256
    8772470c756bdfc6e661045db57805b3b3c0c2303da08fe957e8cd51012af35e
  2. blocked
    Cause
    vercel_deployment_disabled
    Recorded actor
    Vercel
    Mechanism
    deployment_disabled
    Monitor confidence
    95
    Original source timestamp
    2026-10-24 12:32:29.000000
    Evidence SHA-256
    6187feaf28d397a589b2ef045398f6c91d564cb9174f965415b1f2d0f0881c4c
  3. live_content
    Cause
    content_served
    Monitor confidence
    90
    Original source timestamp
    2026-10-24 00:35:13.000000
    Evidence SHA-256
    e1588415d1ca81ba770b6a312fbcb15df27d055dd4c69660fe40ba657785331a
  4. live_content
    Cause
    content_served
    Monitor confidence
    90
    Original source timestamp
    2026-10-23 12:36:17.000000
    Evidence SHA-256
    cb7d8e02544de27e94cb688bb8d4bba91d5f817fb2b1299c2ae9770fe42d136e
  5. unknown
    Cause
    http_2xx_unclassified
    Monitor confidence
    40
    Original source timestamp
    2026-10-23 04:30:24.000000
    Evidence SHA-256
    e15accb76c552c0c023db1fc21ab21ea7a2474b02a95e00538af98b9bad314fb

Recorded activity

4 entries
  1. VirusTotal

    17/92 engine detections

    View source
  2. Added to PhishDestroy

    verication-casefb368-pink.vercel.app

    View source
  3. URLScan

    Page captured

    View source
  4. Wayback Machine

    Page archived

    View source

Check for cloaking

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

verication-casefb368-pink.vercel.app

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Content unavailable
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.

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

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 verication-casefb368-pink.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

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/verication-casefb368-pink.vercel.app"
  title="PhishDestroy threat report for verication-casefb368-pink.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>