Skip to content
https://pornpass.site

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
2
REVIEW
10
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
5 PASS 10 REVIEW 2 FIX
F
HTTP Probe Timing
Action
Total 6399 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
168 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
171 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
6.40 s
Total Time Total request time from DNS lookup through full response.
6.40 s

Connection waterfall

DNS Lookup 33 ms TCP Connect 168 ms TLS Handshake 171 ms Server Processing 6.03 s Content Transfer 0 ms
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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 66.29.146.40 does not match any cert SAN: premium227-5.web-hosting.com
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.
B
Redirect Chain
1 redirect(s), 1198 ms total
REVIEW
1 redirect(s), 1198 ms total
Info::
Single redirect
Got: https://pornpass.site → https://www.pornpass.site/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1198 ms total
Got: 1198 ms

https://pornpass.site

514 ms · HTTP/1.1

301

https://www.pornpass.site/

684 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pornpass.site301514 msHTTP/1.1LiteSpeed
2https://www.pornpass.site/200684 msHTTP/1.1LiteSpeed

See the visual redirect chain in the HTTP Probe tab →

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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.pornpass.site/
200https://pornpass.site/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://pornpass.site/ → https://pornpass.site/

Consistent

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

Certificate validity

47
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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A+
DNS Records
1 A records, 48 ms lookup
PASS
1 A records, 48 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 66.29.146.40
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns1.namecheaphosting.com, dns2.namecheaphosting.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 48 ms
Got: 48 ms
A66.29.146.40
AAAA—
CNAME—
NSdns1.namecheaphosting.com, dns2.namecheaphosting.com
MX
5 mx1-hosting.jellyfish.systems
10 mx2-hosting.jellyfish.systems
20 mx3-hosting.jellyfish.systems
TXT
SPF v=spf1 +a +mx +ip4:66.29.146.35 include:spf.web-hosting.com ~all
CAALookup not available with standard resolver
Resolved in 48 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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 22ms across 3 resolvers (spread 4ms)
PASS
Mean 22ms across 3 resolvers (spread 4ms)
Info::
Quad9: 21ms
Got: 21ms via 9.9.9.9:53
Info::
Cloudflare: 22ms
Got: 22ms via 1.1.1.1:53
Info::
Google: 25ms
Got: 25ms via 8.8.8.8:53
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 118 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 118 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://www.pornpass.site/wp-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 6 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
pornpass.site — via NameCheap, Inc., 5 months old, hosted on Namecheap
PASS
pornpass.site — via NameCheap, Inc., 5 months old, hosted on Namecheap
Info::
Domain registered until Mar 22, 2027 (7 months remaining)
Info::
Domain is only 5 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Mar 22, 2026
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.
Info::
Hosting: Namecheap
Got: AS22612
Domain expiry

208 days

March 22, 2027

SSL certificate

47 days

Issued by Sectigo Limited

Domain age

5 months

Registered March 22, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Namecheap

ASN AS22612

66.29.146.40

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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NameCheap, Inc.
Created March 22, 2026 (5 months ago)
Expires March 22, 2027 (7 months)
Last Updated March 27, 2026
Name Servers dns1.namecheaphosting.com, dns2.namecheaphosting.com
DNSSEC Not enabled
Hosting
IP Address 66.29.146.40
ASN AS22612 (NAMECHEAP-NET - Namecheap, Inc., US)
Provider Namecheap
Data source: rdap (0.8s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback