URLScan截图 · 2026-11-13 16:33 UTC · SHA-256 c5d0d4d7…78bd192
PhishDestroy分析,审阅版
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
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.
PhishDestroy records expressvpn-not-open.pages.dev as a page offering troubleshooting steps for ExpressVPN connectivity problems.
AI摘要
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.
How Do I Fix ExpressVPN Not Connecting to the Internet?
作者
ExpressVPN Support
关键词
ExpressVPN not connecting, VPN issues, Fix VPN internet, ExpressVPN troubleshooting, VPN no internet
描述
Having trouble with ExpressVPN not connecting to the internet? Follow this step-by-step guide to fix VPN connectivity issues quickly.
追踪器
请求
2
检测到的服务
名称
Zendesk CDN
公司
Zendesk
国家/地区
US
类别
托管
请求
1
表单与混合内容
无 SRI 的脚本
https://static.zdassets.com/ekr/snippet.js
第三方脚本
1
HTTP 响应
可访问
是
HTTP状态码
200
请求耗时(毫秒)
DNS
4
TLS
68
等待
74
连接
10
下载
0
响应时间(毫秒)
156
TLS连接
ALPN
h2
加密套件
TLS_AES_256_GCM_SHA384
协议
TLSv1.3
支持的版本
TLSv1.2
TLSv1.3
证书已验证
是
前向保密
是
端口
开放端口
80
443
8080
碳排放估算
字节
6518
CO₂(克)
0.0002
比其他页面更环保的比例(%)
81
DNS 服务器
域名服务器
IP 地址
162.159.38.19
主机
surina.ns.cloudflare.com
IP 地址
162.159.44.20
主机
rommy.ns.cloudflare.com
DNS 区域
expressvpn-not-open.pages.dev
位置
IP 地址
2a06:98c1:3121::3
ASN
13335
组织
CloudFLARENET-EU
城市
London
国家/地区
GB
TLS 证书
签发者
Google Trust Services / WE1
使用者(Subject)
expressvpn-not-open.pages.dev
DNS 记录
A
188.114.97.3
188.114.96.3
NS
surina.ns.cloudflare.com
rommy.ns.cloudflare.com
SOA
主域名服务器
rommy.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
序列号
2419855203
刷新(秒)
10000
重试(秒)
2400
过期(秒)
604800
最小 TTL(秒)
1800
AAAA
2a06:98c1:3121::3
2a06:98c1:3120::3
DNSSEC
DS 记录
否
RRSIG
否
DNSKEY
否
HSTS
观测结果
Site does not serve any HSTS headers.
HTTP 安全策略
X-Frame-Options
否
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
否
Permissions-Policy
否
X-Content-Type-Options
nosniff
Content-Security-Policy
否
Strict-Transport-Security
否
Cross-Origin-Opener-Policy
否
Cross-Origin-Embedder-Policy
否
Cross-Origin-Resource-Policy
否
Web 应用防火墙
WAF 产品
Cloudflare
检测到 WAF
是
IP 查询
IP 地址
2a06:98c1:3121::3
IP 版本
6
重定向
重定向链
https://expressvpn-not-open.pages.dev
技术栈
技术
Sentry
Zendesk
HSTS
Cloudflare
Webpack
Module Federation
HTTP/3
TLS 配置测试
评分
A
状态
READY
页面链接
外部链接地址
https://expressvpns.support/
外部链接
1
HTTP 头
响应头
服务器
cloudflare
Content-Type
text/html; charset=utf-8
X-Content-Type-Options
nosniff
Referrer-Policy
strict-origin-when-cross-origin
来源原始字段 · JSON
邮件配置
Spf lookups: 0
DNS防护结果
Resolvers: 12; Blocked count: 0
页面标题与元数据
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.
证据层Availability: Content servingContent: Content served at rootDNS: Stale
最新的 HTTP 观察结果内容在线提供普通 HTTP 内容90%2026-11-22 11:10 UTC
RDAP注册
观测时间线last reachable: 2026-11-22 11:10 UTClast 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.