Skip to content
https://pornoadvisor.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
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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 94.23.66.84 does not match any cert SAN: cluster031.hosting.ovh.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 lookup failed for 2001:41d0:301:11::31: lookup 2001:41d0:301:11::31: 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 28 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 28 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /go/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.pornoadvisor.com/
200https://pornoadvisor.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

C
TLS Certificate Expiry & Recommendations
Action
26 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

26
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 26 days remaining
  • 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, 45 ms lookup
PASS
1 A records, 45 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 94.23.66.84
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: 2001:41d0:301:11::31
Info::
6 nameserver(s) configured
Got: ns1.dominiofaidate.com, ns3.dominiofaidate.com, ns6.dominiofaidate.com, ns5.dominiofaidate.com, ns2.dominiofaidate.com, ns4.dominiofaidate.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 45 ms
Got: 45 ms
A94.23.66.84
AAAA2001:41d0:301:11::31
CNAME—
NSns1.dominiofaidate.com, ns3.dominiofaidate.com, ns6.dominiofaidate.com, ns5.dominiofaidate.com, ns2.dominiofaidate.com, ns4.dominiofaidate.com
MX
10 mail.pornoadvisor.com
TXT
SPF v=spf1 a mx -all
google-site-verification=b8sZGtcSfB3bSSfy6hP8vHGyndTjGQ84ukgQLgch4_c
CAALookup not available with standard resolver
Resolved in 45 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 44ms)
PASS
Mean 22ms across 3 resolvers (spread 44ms)
Info::
Quad9: 0ms
Got: 0ms via 9.9.9.9:53
Info::
Cloudflare: 22ms
Got: 22ms via 1.1.1.1:53
Info::
Google: 44ms
Got: 44ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 247 ms total
PASS
1 redirect(s), 247 ms total
Info::
Single redirect
Got: https://pornoadvisor.com → https://www.pornoadvisor.com/ (301)
Info::
WWW normalization redirect

https://pornoadvisor.com

68 ms · HTTP/1.1

301

https://www.pornoadvisor.com/

179 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pornoadvisor.com30168 msHTTP/1.1Apache
2https://www.pornoadvisor.com/200179 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (20 ms)
PASS
IPv6 reachable (20 ms)
Info::
IPv6 is configured and reachable at 2001:41d0:301:11::31
Got: 20 ms connect
IPv6 Ready
AAAA Records 2001:41d0:301:11::31 Connection Reachable (20 ms)
A+
Domain Intelligence
pornoadvisor.com — via PDR Ltd. d/b/a PublicDomainRegistry.com, 9 years, 9 months old
PASS
pornoadvisor.com — via PDR Ltd. d/b/a PublicDomainRegistry.com, 9 years, 9 months old
Info::
Domain registered until Jan 2, 2027 (4 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: PDR Ltd. d/b/a PublicDomainRegistry.com
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

139 days

January 2, 2027

SSL certificate

26 days

Issued by Let's Encrypt

Domain age

9 years, 9 months

Registered January 2, 2017

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2001:41d0:301:11::31

Registrar

PDR Ltd. d/b/a PublicDomainRegistry.com

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar PDR Ltd. d/b/a PublicDomainRegistry.com
Created January 2, 2017 (9 years, 9 months ago)
Expires January 2, 2027 (4 months)
Last Updated November 21, 2025
Name Servers ns1.dominiofaidate.com, ns2.dominiofaidate.com, ns3.dominiofaidate.com, ns4.dominiofaidate.com, ns5.dominiofaidate.com, ns6.dominiofaidate.com
DNSSEC Not enabled
Hosting
IP Address 2001:41d0:301:11::31
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 120 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
53 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
20 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
26 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
121 ms
Total Time Total request time from DNS lookup through full response.
121 ms

Connection waterfall

DNS Lookup 53 ms TCP Connect 20 ms TLS Handshake 26 ms Server Processing 22 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