Skip to content
https://xvideos.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
7 PASS 9 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/15 IPs match cert SAN
REVIEW
0/15 IPs match cert SAN
Info::
PTR for 89.222.127.9 does not match any cert SAN: unn-89-222-127-9.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.11 does not match any cert SAN: unn-89-222-127-11.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.3 does not match any cert SAN: unn-89-222-127-3.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.15 does not match any cert SAN: unn-89-222-127-15.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.1 does not match any cert SAN: unn-89-222-127-1.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.5 does not match any cert SAN: unn-89-222-127-5.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.14 does not match any cert SAN: unn-89-222-127-14.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.13 does not match any cert SAN: unn-89-222-127-13.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.7 does not match any cert SAN: unn-89-222-127-7.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.10 does not match any cert SAN: unn-89-222-127-10.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.4 does not match any cert SAN: unn-89-222-127-4.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.8 does not match any cert SAN: unn-89-222-127-8.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.6 does not match any cert SAN: unn-89-222-127-6.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.2 does not match any cert SAN: unn-89-222-127-2.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 89.222.127.12 does not match any cert SAN: unn-89-222-127-12.wgcz.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.xvideos.com/
200https://xvideos.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://xvideos.com/ → https://www.xvideos.com/

Consistent

B
TLS Certificate Expiry & Recommendations
247 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

247
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
15 A records, 31 ms lookup
PASS
15 A records, 31 ms lookup
Info::
Resolves to 15 IPv4 address(es)
Got: 89.222.127.9, 89.222.127.11, 89.222.127.3, 89.222.127.15, 89.222.127.1, 89.222.127.5, 89.222.127.14, 89.222.127.13, 89.222.127.7, 89.222.127.10, 89.222.127.4, 89.222.127.8, 89.222.127.6, 89.222.127.2, 89.222.127.12
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns2.wgcz.net, ns3.wgcz.net, ns1.wgcz.net
Info::
7 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 31 ms
Got: 31 ms
A89.222.127.9, 89.222.127.11, 89.222.127.3, 89.222.127.15, 89.222.127.1, 89.222.127.5, 89.222.127.14, 89.222.127.13, 89.222.127.7, 89.222.127.10, 89.222.127.4, 89.222.127.8, 89.222.127.6, 89.222.127.2, 89.222.127.12
AAAA—
CNAME—
NSns2.wgcz.net, ns3.wgcz.net, ns1.wgcz.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx4.googlemail.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
10 aspmx5.googlemail.com
TXT
SPF v=spf1 mx ip4:79.127.140.143 ip4:79.127.140.144 ip4:79.127.140.145 include:_spf....
tiktok-developers-site-verification=TjYXWYDF1LPiMRRgAh2HYTW06oWK9hbW
google-site-verification=AaqKS4MdHV6EpISaFwBtduOlvf79g3Wx5QxzTIl1ECQ
CAALookup not available with standard resolver
Resolved in 31 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 11ms across 3 resolvers (spread 17ms)
PASS
Mean 11ms across 3 resolvers (spread 17ms)
Info::
Quad9: 0ms
Got: 0ms via 9.9.9.9:53
Info::
Google: 16ms
Got: 16ms via 8.8.8.8:53
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
A
Redirect Chain
1 redirect(s), 215 ms total
PASS
1 redirect(s), 215 ms total
Info::
Single redirect
Got: https://xvideos.com → https://www.xvideos.com/ (301)
Info::
WWW normalization redirect

https://xvideos.com

84 ms · HTTP/1.1

301

https://www.xvideos.com/

132 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://xvideos.com30184 msHTTP/1.1nginx
2https://www.xvideos.com/200132 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 17 URLs
PASS
robots.txt present, sitemap with 17 URLs
Info::
robots.txt is present
Got: 61 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 17 entries
Info::
Sitemap index with 17 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 61 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-Agent: *    
Disallow: /video-vote/
Disallow: /account/
sitemap.xml 200 OK
Type Sitemap Index URLs 17 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
xvideos.com — via Gransy, s.r.o., 28 years, 9 months old, hosted on CDN77 - Datacamp Limited, GB
PASS
xvideos.com — via Gransy, s.r.o., 28 years, 9 months old, hosted on CDN77 - Datacamp Limited, GB
Info::
Domain registered until Dec 29, 2028 (2 years, 7 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Gransy, s.r.o.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: CDN77 - Datacamp Limited, GB
Got: AS60068
Domain expiry

947 days

December 29, 2028

SSL certificate

247 days

Issued by Sectigo Limited

Domain age

28 years, 9 months

Registered December 30, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CDN77 - Datacamp Limited, GB

ASN AS60068

89.222.127.15

Registrar

Gransy, s.r.o.

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Gransy, s.r.o.
Created December 30, 1997 (28 years, 9 months ago)
Expires December 29, 2028 (2 years, 7 months)
Last Updated January 30, 2026
Name Servers ns1.wgcz.net, ns2.wgcz.net, ns3.wgcz.net
DNSSEC Not enabled
Hosting
IP Address 89.222.127.15
ASN AS60068 (CDN77 - Datacamp Limited, GB)
Provider CDN77 - Datacamp Limited, GB
Data source: rdap (0.5s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 106 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
22 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
25 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
28 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
106 ms
Total Time Total request time from DNS lookup through full response.
106 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 25 ms TLS Handshake 28 ms Server Processing 31 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback