Skip to content
https://pornsavr.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 8 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.

C
DNSSEC
Action
Zone signed but parent has no DS record
REVIEW
Zone signed but parent has no DS record
Warning::
DNSSEC keys published but parent zone has no DS record
The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.
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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 93.188.2.55 does not match any cert SAN: webfront5.webcluster.loopia.se
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 2a02:250:0:8::52 does not match any cert SAN: webfront2.webcluster.loopia.se
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
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.pornsavr.com/
200https://pornsavr.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://pornsavr.com/ → https://pornsavr.com/

Consistent

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

Certificate validity

40
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
1 A records, 62 ms lookup
PASS
1 A records, 62 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 93.188.2.55
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a02:250:0:8::52
Info::
2 nameserver(s) configured
Got: ns1.loopia.se, ns2.loopia.se
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 62 ms
Got: 62 ms
A93.188.2.55
AAAA2a02:250:0:8::52
CNAME—
NSns1.loopia.se, ns2.loopia.se
MX
10 mailcluster.loopia.se
20 mail2.loopia.se
TXT
google-site-verification=5eZeOapQTvv2fbXODb1RZTm1q4Hs1-M_ujWvvMBvPQg
SPF v=spf1 include:spf.loopia.se -all
CAALookup not available with standard resolver
Resolved in 62 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 82ms across 3 resolvers (spread 64ms)
PASS
Mean 82ms across 3 resolvers (spread 64ms)
Info::
Google: 51ms
Got: 51ms via 8.8.8.8:53
Info::
Cloudflare: 80ms
Got: 80ms via 1.1.1.1:53
Info::
Quad9: 115ms
Got: 115ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://pornsavr.com

https://pornsavr.com

307 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pornsavr.com200307 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (50 ms)
PASS
IPv6 reachable (50 ms)
Info::
IPv6 is configured and reachable at 2a02:250:0:8::52
Got: 50 ms connect
IPv6 Ready
AAAA Records 2a02:250:0:8::52 Connection Reachable (50 ms)
A+
Crawlability
robots.txt present, sitemap with 3335 URLs
PASS
robots.txt present, sitemap with 3335 URLs
Info::
robots.txt is present
Got: 65 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3335 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 65 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://pornsavr.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 3335 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
pornsavr.com — via GoDaddy.com, LLC, 4 years, 9 months old
PASS
pornsavr.com — via GoDaddy.com, LLC, 4 years, 9 months old
Info::
Domain registered until Nov 18, 2026 (3 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: GoDaddy.com, LLC
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

94 days

November 18, 2026

SSL certificate

40 days

Issued by Let's Encrypt

Domain age

4 years, 9 months

Registered November 18, 2021

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:250:0:8::52

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created November 18, 2021 (4 years, 9 months ago)
Expires November 18, 2026 (3 months)
Last Updated November 18, 2025
Name Servers ns1.loopia.se, ns2.loopia.se
DNSSEC Not enabled
Hosting
IP Address 2a02:250:0:8::52
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 64 ms TCP Connect 48 ms TLS Handshake 52 ms Server Processing 212 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback