Infrastructure - https://legalporno.com BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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)

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)

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/3 IPs match cert SAN

REVIEW

0/3 IPs match cert SAN

PTR lookup failed for 185.120.70.197: lookup 185.120.70.197: 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.

PTR lookup failed for 185.120.68.181: lookup 185.120.68.181: 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.

PTR lookup failed for 185.120.70.213: lookup 185.120.70.213: 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.

C

Multi-Resolver DNS Speed

Action

Mean 147ms across 3 resolvers (spread 272ms)

REVIEW

Mean 147ms across 3 resolvers (spread 272ms)

Quad9: 1ms

Got: 1ms via 9.9.9.9:53

Cloudflare: 169ms

Got: 169ms via 1.1.1.1:53

Google: 273ms

Got: 273ms via 8.8.8.8:53

High latency spread between resolvers: 272ms (min 1ms / max 273ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

B

Redirect Chain

1 redirect(s), 1513 ms total

REVIEW

1 redirect(s), 1513 ms total

Single redirect

Got: https://legalporno.com → https://www.analvids.com/ (301)

WWW normalization redirect

Redirect overhead: 1513 ms total

Got: 1513 ms

Cross-domain redirect detected

https://legalporno.com

871 ms · HTTP/1.1

301

https://www.analvids.com/

642 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://legalporno.com	301	871 ms	HTTP/1.1	nginx
2	https://www.analvids.com/	200	642 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

www/non-www redirect configured correctly (preferred: non-www)

HTTP version does not redirect to HTTPS

Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

301https://www.legalporno.com/

200https://legalporno.com/

Preferred variant: non-www

HTTP → HTTPS

301http://legalporno.com/ → http://www.analvids.com/

HTTP version does not redirect to HTTPS

B

HTTP Probe Timing

Total 827 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

334 ms

TCP Connect

160 ms

TLS Handshake

174 ms

Time to First Byte

827 ms

Total Time

828 ms

Connection waterfall

DNS Lookup 334 ms TCP Connect 160 ms TLS Handshake 174 ms Server Processing 160 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

35 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

35

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

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

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

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: 429, /healthz: 429, /ping: 404, /status: 404.

A

DNS Records

3 A records, 334 ms lookup

PASS

3 A records, 334 ms lookup

Resolves to 3 IPv4 address(es)

Got: 185.120.70.197, 185.120.68.181, 185.120.70.213

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns4.cloudevelops.org, ns2.cloudevelops.com, ns1.cloudevelops.cz, ns3.cloudevelops.net

2 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (334 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 334 ms

A	185.120.70.197, 185.120.68.181, 185.120.70.213
AAAA	—
CNAME	—
NS	ns4.cloudevelops.org, ns2.cloudevelops.com, ns1.cloudevelops.cz, ns3.cloudevelops.net
MX	100 mx-1.cloudevelops.com 200 mx-2.cloudevelops.com
TXT	SPF v=spf1 a mx include:mail.zendesk.com ip4:185.120.68.0/22 -all
CAA	Lookup not available with standard resolver

Resolved in 334 ms

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A

Crawlability

robots.txt present, sitemap with 0 URLs

PASS

robots.txt present, sitemap with 0 URLs

robots.txt is present

Got: 2003 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml is empty — no URLs found

An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt references sitemap

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK

Size 2003 B Sitemaps referenced 1 User-agents Googlebot, Yandex, bingbot, * Blocking No — crawling allowed

User-agent: *
Disallow: /api/
Disallow: /index/filter
Disallow: /member-area
Disallow: /studios/*/latest
Disallow: /search/
Disallow: /forum/adm
Disallow: /forum/cache
Disallow: /forum/files
Disallow: /forum/includes
Disallow: /forum/language
Disallow: /forum/store
Disallow: /forum/cron.php
Disallow: /forum/download/file.php
Disallow: /forum/karma.php
Disallow: /forum/memberlist.php
Disallow: /forum/posting.php
Disallow: /forum/search.php
Disallow: /forum/ucp.php
Crawl-delay: 5
Host:www.analvids.com/
Sitemap:https://www.analvids.com/sitemap.xml
User-Agent: Googlebot
Disallow: /api/
Disallow: /index/filter
Disallow: /member-area
Disallow: /studios/*/latest
Disallow: /search/
Disallow: /forum/adm
Disallow: /forum/cache
Disallow: /forum/files
Disallow: /forum/includes
Disallow: /forum/language
Disallow: /forum/store
Disallow: /forum/cron.php
Disallow: /forum/download/file.php
Disallow: /forum/karma.php
Disallow: /forum/memberlist.php
Disallow: /forum/posting.php
Disallow: /forum/search.php
Disallow: /forum/ucp.php
User-Agent: Yandex
Disallow: /api/
Disallow: /index/filter
Disallow: /member-area
Disallow: /studios/*/latest
Disallow: /search/
Disallow: /forum/adm
Disallow: /forum/cache
Disallow: /forum/files
Disallow: /forum/includes
Disallow: /forum/language
Disallow: /forum/store
Disallow: /forum/cron.php
Disallow: /forum/download/file.php
Disallow: /forum/karma.php
Disallow: /forum/memberlist.php
Disallow: /forum/posting.php
Disallow: /forum/search.php
Disallow: /forum/ucp.php
Crawl-delay: 1
User-Agent: bingbot
Disallow: /api/
Disallow: /index/filter
Disallow: /member-area
Disallow: /studios/*/latest
Disallow: /search/
Disallow: /forum/adm
Disallow: /forum/cache
Disallow: /forum/files
Disallow: /forum/includes
Disallow: /forum/language
Disallow: /forum/store
Disallow: /forum/cron.php
Disallow: /forum/download/file.php
Disallow: /forum/karma.php
Disallow: /forum/memberlist.php
Disallow: /forum/posting.php
Disallow: /forum/search.php
Disallow: /forum/ucp.php
Crawl-delay: 1

sitemap.xml 200 OK

Type URL Set URLs 0 entries Valid XML Yes

A+

Domain Intelligence

legalporno.com — via eNom, LLC, 16 years, 4 months old, hosted on cloudinfrastack - cloudinfrastack, s.r.o., CZ

PASS

legalporno.com — via eNom, LLC, 16 years, 4 months old, hosted on cloudinfrastack - cloudinfrastack, s.r.o., CZ

Domain registered until May 14, 2027 (10 months remaining)

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.

Registrar: eNom, LLC

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.

Hosting: cloudinfrastack - cloudinfrastack, s.r.o., CZ

Got: AS8646

Domain expiry

306 days

May 14, 2027

SSL certificate

35 days

Issued by Let's Encrypt

Domain age

16 years, 4 months

Registered May 14, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

cloudinfrastack - cloudinfrastack, s.r.o., CZ

ASN AS8646

185.120.70.197

Registrar

eNom, LLC

Unlocked 4 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 eNom, LLC

Created May 14, 2010 (16 years, 4 months ago)

Expires May 14, 2027 (10 months)

Last Updated April 15, 2026

Name Servers ns1.cloudevelops.cz, ns2.cloudevelops.com, ns3.cloudevelops.net, ns4.cloudevelops.org

DNSSEC Not enabled

Hosting

IP Address 185.120.70.197

ASN AS8646 (cloudinfrastack - cloudinfrastack, s.r.o., CZ)

Provider cloudinfrastack - cloudinfrastack, s.r.o., CZ

Data source: rdap (1.9s)

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