Skip to security report
Dangerous

Phishing copy of Expressvpn

expressvpn-not-open.pages.dev favicon
Domain security and threat intelligence

expressvpn-not-open.pages.dev

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy records expressvpn-not-open.pages.dev as a page offering troubleshooting steps for ExpressVPN connectivity problems.

Page title: “How Do I Fix ExpressVPN Not Connecting to the Internet?”

More about the sources
Recorded security signals

Use caution — do not enter credentials or personal information.

Resolved IP
Canada188.114.96.3CloudFlare, Inc. · CDN
First seen by PhishDestroy
2026-11-13
Page captures
open gallery
2026-11-14 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Critical
Status
Last known active
Hosting
Canada188.114.96.3CloudFlare, Inc. · CDN
Page captures
9

URLScan capture · 2026-11-13 16:33 UTC · SHA-256 c5d0d4d7…78bd192

PhishDestroy analysis, reviewed version

expressvpn-not-open.pages.dev displays an article titled "How Do I Fix ExpressVPN Not Connecting to the Internet?" The page presents numbered troubleshooting steps for users whose VPN connection blocks internet access, including checking the basic connection, restarting the ExpressVPN app, switching server locations, changing the VPN protocol, temporarily disabling antivirus or firewall software, flushing DNS and resetting network settings, and trying a different network.

The stored VirusTotal domain result reports 0 detections out of 92 engines.

Source evidence 4 sources

URLScan

Malicious

SHA-256 925bf234…7c7e7fc

Open report
URLScanOriginal source recordObserved: 19 fields
Separate monitor record · 2026-11-14 04:30 UTC

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

UUID
01a1d74a-b89e-7561-b299-dfd690c4c417
Score
100
Malicious
✓
Result at
2026-11-14T04:30:29Z
Enriched at
2026-11-14T09:13:45Z
Source timestamps
Urlscan result at: 2026-11-14 05:30:29; Urlscan enriched at: 2026-11-14 10:13:45

PhishDestroy DOM

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

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-11-14 02:48 UTC

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

Heuristic score
10
Analyzed at
2026-11-14T02:48:40Z
Source timestamp
2026-11-14 03:48:40
Technical metadata

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
expressvpn-not-open.pages.dev: ExpressVPN Troubleshooting Guide
AI description
PhishDestroy records expressvpn-not-open.pages.dev as a page offering troubleshooting steps for ExpressVPN connectivity problems.
AI summary
expressvpn-not-open.pages.dev displays an article titled "How Do I Fix ExpressVPN Not Connecting to the Internet?" The page presents numbered troubleshooting steps for users whose VPN connection blocks internet access, including checking the basic connection, restarting the ExpressVPN app, switching server locations, changing the VPN protocol, temporarily disabling antivirus or firewall software, flushing DNS and resetting network settings, and trying a different network. The stored VirusTotal domain result reports 0 detections out of 92 engines.
AI generated by
threat-v6-mimo
AI generated at
2026-11-14T02:48:32Z
Revision
371b209a08f4b3782340fc6979da391afa62da22a901e4e53f0782413f064b15
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
VirusTotalOriginal source recordObserved: 13 fields
Open complete records
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Page title
How Do I Fix ExpressVPN Not Connecting to the Internet?
Author
ExpressVPN Support
Keywords
ExpressVPN not connecting, VPN issues, Fix VPN internet, ExpressVPN troubleshooting, VPN no internet
Description
Having trouble with ExpressVPN not connecting to the internet? Follow this step-by-step guide to fix VPN connectivity issues quickly.

Trackers

Requests
2
Observed services
  • Name
    Zendesk CDN
    Company
    Zendesk
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://static.zdassets.com/ekr/snippet.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
4
TLS
68
Waiting
74
Connection
10
Download
0
Response time, ms
156

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
6518
CO₂, grams
0.0002
Cleaner than, %
81

DNS servers

Nameservers
  • IP address
    162.159.38.19
    Host
    surina.ns.cloudflare.com
  • IP address
    162.159.44.20
    Host
    rommy.ns.cloudflare.com
DNS zone
expressvpn-not-open.pages.dev

Location

IP address
2a06:98c1:3121::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Google Trust Services / WE1
Subject
expressvpn-not-open.pages.dev

DNS records

A
  • 188.114.97.3
  • 188.114.96.3
NS
  • surina.ns.cloudflare.com
  • rommy.ns.cloudflare.com
SOA
Primary nameserver
rommy.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2419855203
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3121::3
IP version
6

Redirects

Redirect chain
  • https://expressvpn-not-open.pages.dev

Technology stack

Technologies
  • Sentry
  • Zendesk
  • HSTS
  • Cloudflare
  • Webpack
  • Module Federation
  • HTTP/3

TLS configuration test

Grades
  • A
Status
READY

Page links

External link addresses
  • https://expressvpns.support/
External links
1

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=utf-8
X-Content-Type-Options
nosniff
Referrer-Policy
strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Page title and metadata
Title: How Do I Fix ExpressVPN Not Connecting to the Internet?; Author: ExpressVPN Support; Keywords: ExpressVPN not connecting, VPN issues, Fix VPN internet, ExpressVPN troubleshooting, VPN no internet; Description: Having trouble with ExpressVPN not connecting to the internet? Follow this step-by-step guide to fix VPN connectivity issues quickly.
Trackers
Requests: 2; Trackers: (Name: Zendesk CDN; Company: Zendesk; Country: US; Category: Hosting; Requests: 1)
Forms and mixed content
No sri: https://static.zdassets.com/ekr/snippet.js; Third party scripts: 1
Status
Up: ✓; Code: 200; Timings: DNS: 4; TLS: 68; Wait: 74; Connect: 10; Download: 0; Response ms: 156
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 6518; Co2 grams: 0.0002; Cleaner than: 81
DNS server
NS: (IP: 162.159.38.19; Host: surina.ns.cloudflare.com), (IP: 162.159.44.20; Host: rommy.ns.cloudflare.com); Zone: expressvpn-not-open.pages.dev
Location
IP: 2a06:98c1:3121::3; ASN: 13335; Org: CloudFLARENET-EU; City: London; Country: GB
SSL
Issuer: Google Trust Services / WE1; Subject: expressvpn-not-open.pages.dev
DNS records
A: 188.114.97.3, 188.114.96.3; NS: surina.ns.cloudflare.com, rommy.ns.cloudflare.com; Soa: Nsname: rommy.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2419855203; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2a06:98c1:3121::3, 2a06:98c1:3120::3
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: strict-origin-when-cross-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2a06:98c1:3121::3; Family: 6
Redirects
Chain: https://expressvpn-not-open.pages.dev
Tech stack
Technologies: Sentry, Zendesk, HSTS, Cloudflare, Webpack, Module Federation, HTTP/3
TLS labs
Grades: A; Status: READY
Page links
External: https://expressvpns.support/; External count: 1
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=utf-8; X content type options: nosniff; Referrer policy: strict-origin-when-cross-origin

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (9)

All capture links and hashes (9)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Fakesupport report ↗
IP Context Canada188.114.96.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider pages.dev
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-14
DOM Analysisanalyzed 2026-11-14score 10/1001 brand signal
Submitted URLhttps://expressvpn-not-open.pages.dev/
Favicon Hash
Observed page title
How Do I Fix ExpressVPN Not Connecting to the Internet?
Automated brand references
Expressvpn
TLS Certificate
Issued by WE1 · stored validity ends in 78 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada188.114.96.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
CloudFlare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • rommy.ns.cloudflare.com
  • surina.ns.cloudflare.com

SOA

  • nsname: rommy.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2419855203
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-11-11 02:58:08
Valid until
2027-02-09 03:55:46
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate names · 2 SANs
  • expressvpn-not-open.pages.dev
  • *.expressvpn-not-open.pages.dev

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-11-22 11:10 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-22 11:10 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:10 UTC last content: 2026-11-22 11:10 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 4 identified
Open complete records
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: https://expressvpn-not-open.pages.dev/
How Do I Fix ExpressVPN Not Connecting to the Internet?
Having trouble with ExpressVPN not connecting to the internet? Follow this step-by-step guide to fix VPN connectivity issues quickly.
Response
HTTP 200
HTML body
6.4 KB
Compressed
2.7 KB
Links
0 internal · 1 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Server: cloudflare
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 81a67def7af176826fa8661ba83ecab5c94c8bd0c3a9e4f3a8238abefed32fac
Saved response-header values · 14
Access-Control-Allow-Origin
*
Alt-Svc
h3=":443"; ma=86400
Cache-Control
public, max-age=0, must-revalidate
CF-RAY
a5a2b581ce8112fa-AMS
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 14 Nov 2026 02:50:30 GMT
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Referrer-Policy
strict-origin-when-cross-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=GJVxXViVoVaXrDvrR3pC9bTdFbXJfZ86A4UE6Z68mdirE%2Bb8b2vBqEvZ%2FFBuPsyyy7pAd4DapGJbmIW3JxS6DO9rp9NiMNdxLMl0aE28yLZ%2F8PlR6L1kKXbDRaqwtdwrWISkzkw6f
Server
cloudflare
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff

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

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

All stored data100
Open complete records

Captured network requests

Network requests: 6 SHA-256 hashes: 6 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-14 02:43 UTC.

Open this scan on URLScan 01a1d74a-b89e-7561-b299-dfd690c4c417 ↗

Stored observation history2

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

    Serving page content

    page content returned

  2. Domain monitor · First collection record

    Reachable

All retained availability observations20
Open complete records

Threat Response Pipeline

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

Recorded events: 8. 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
  • Threat Ingested
    expressvpn-not-open.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Automated brand label: Expressvpn · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

2 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+2263 d 21 h
  1. Added to PhishDestroy

    expressvpn-not-open.pages.dev

    same minute
  2. URLScan

    Page captured

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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

expressvpn-not-open.pages.dev

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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. Secure your accounts and funds first, then report. 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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 expressvpn-not-open.pages.dev)
  • 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

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.

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/expressvpn-not-open.pages.dev"
  title="PhishDestroy threat report for expressvpn-not-open.pages.dev"
  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>