Skip to content
https://theporndude.vip

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
6
PASS
10
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
10 PASS 6 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:3033::ac43:aa29, 2606:4700:3033::6815:1c10
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3033::ac43:aa29]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2606:4700:3033::ac43:aa29, 2606:4700:3033::6815:1c10 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 172.67.170.41: lookup 172.67.170.41: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.21.28.16: lookup 104.21.28.16: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3033::ac43:aa29: lookup 2606:4700:3033::ac43:aa29: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3033::6815:1c10: lookup 2606:4700:3033::6815:1c10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
54 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
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: connection error, /healthz: connection error, /ping: 404, /status: connection error.
A+
DNS Records
2 A records, 15 ms lookup
PASS
2 A records, 15 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.170.41, 104.21.28.16
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3033::ac43:aa29, 2606:4700:3033::6815:1c10
Info::
2 nameserver(s) configured
Got: jean.ns.cloudflare.com, max.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 15 ms
Got: 15 ms
A172.67.170.41, 104.21.28.16
AAAA2606:4700:3033::ac43:aa29, 2606:4700:3033::6815:1c10
CNAME—
NSjean.ns.cloudflare.com, max.ns.cloudflare.com
MX
10 mail.myteam.network
TXT
google-site-verification=4ytjYChnKAY3129B8jNkMDhDQvxwJJlojWuEArNwZuo
google-site-verification=IsqmImYOZx33njl_FdeThmPvn0fKdnXHEzOPIyGdy5Q
google-site-verification=dntnP5COjbodpE2bLL5v5J8hpGsmDgkNYes_YwdfCqY
google-site-verification=y-pNZzJ6oF_H4G3qRWfCVWezb4wySl5j3ZLRG23Vnpk
SPF v=spf1 mx ip4:3.9.214.250 ~all
CAALookup not available with standard resolver
Resolved in 15 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 6ms across 3 resolvers (spread 7ms)
PASS
Mean 6ms across 3 resolvers (spread 7ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 5ms
Got: 5ms via 9.9.9.9:53
Info::
Google: 11ms
Got: 11ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://theporndude.vip

https://theporndude.vip

83 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://theporndude.vip20083 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 15 URLs
PASS
robots.txt present, sitemap with 15 URLs
Info::
robots.txt is present
Got: 113 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 15 entries
Info::
Sitemap index with 15 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 113 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://theporndude.vip/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 15 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.theporndude.vip/
200https://theporndude.vip/

Preferred variant: non-www

HTTP → HTTPS

301http://theporndude.vip/ → https://theporndude.vip/

Consistent

A+
Domain Intelligence
theporndude.vip — via NameCheap, Inc., 6 years, 5 months old
PASS
theporndude.vip — via NameCheap, Inc., 6 years, 5 months old
Info::
Domain registered until May 23, 2027 (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: NameCheap, Inc.
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.
Domain expiry

215 days

May 23, 2027

SSL certificate

54 days

Issued by Google Trust Services

Domain age

6 years, 5 months

Registered May 23, 2020

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3033::6815:1c10

Registrar

NameCheap, Inc.

Unlocked 2 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 NameCheap, Inc.
Created May 23, 2020 (6 years, 5 months ago)
Expires May 23, 2027 (7 months)
Last Updated September 5, 2026
Name Servers jean.ns.cloudflare.com, max.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3033::6815:1c10
Data source: rdap (0.6s)

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 84 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
23 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
79 ms
Total Time Total request time from DNS lookup through full response.
84 ms

Connection waterfall

DNS Lookup 23 ms TCP Connect 2 ms TLS Handshake 11 ms Server Processing 45 ms Content Transfer 5 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Document is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: a4d2736dba805417-GRU
Info::
CDN cache status: HIT
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: a4d2736dba805417-GRU
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=20074, cf-cache-status=HIT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback