Skip to content
https://toppornguide.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 8 REVIEW
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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 141.193.213.11: lookup 141.193.213.11: 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 141.193.213.10: lookup 141.193.213.10: 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
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
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 429 Expected: 301 redirect to HTTPS

www / non-www

301https://www.toppornguide.com/
200https://toppornguide.com/

Preferred variant: non-www

HTTP → HTTPS

429http://toppornguide.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

77
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
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
2 A records, 45 ms lookup
PASS
2 A records, 45 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 141.193.213.11, 141.193.213.10
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1106.awsdns-10.org, ns-369.awsdns-46.com, ns-2032.awsdns-62.co.uk, ns-602.awsdns-11.net
Info::
4 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 45 ms
Got: 45 ms
A141.193.213.11, 141.193.213.10
AAAA—
CNAME—
NSns-1106.awsdns-10.org, ns-369.awsdns-46.com, ns-2032.awsdns-62.co.uk, ns-602.awsdns-11.net
MX
10 a008362.mx.mailhop.org
20 mx1.mailhop.us
30 mx1.mailhop.co
40 mx1.mailhop.co.uk
TXT
google-site-verification=6ipVt5KmB_XmnscLHPGltywdgrFVTypFmC7js2l_Iz0
SPF v=spf1 include:spf.privateemail.com ~all
CAALookup not available with standard resolver
Resolved in 45 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 47ms across 3 resolvers (spread 58ms)
PASS
Mean 47ms across 3 resolvers (spread 58ms)
Info::
Google: 19ms
Got: 19ms via 8.8.8.8:53
Info::
Cloudflare: 45ms
Got: 45ms via 1.1.1.1:53
Info::
Quad9: 77ms
Got: 77ms 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://toppornguide.com

https://toppornguide.com

44 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://toppornguide.com20044 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 70 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 does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 70 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php
sitemap.xml 200 OK
Type Sitemap Index URLs 6 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
toppornguide.com — via GoDaddy.com, LLC, 11 years old, hosted on Cloudflare
PASS
toppornguide.com — via GoDaddy.com, LLC, 11 years old, hosted on Cloudflare
Info::
Domain registered until Sep 16, 2027 (1 years, 1 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.
Info::
Hosting: Cloudflare
Got: AS209242
Domain expiry

403 days

September 16, 2027

SSL certificate

77 days

Issued by Let's Encrypt

Domain age

11 years

Registered September 16, 2015

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS209242

141.193.213.10

Registrar

GoDaddy.com, 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 GoDaddy.com, LLC
Created September 16, 2015 (11 years ago)
Expires September 16, 2027 (1 years, 1 months)
Last Updated June 8, 2026
Name Servers ns-1106.awsdns-10.org, ns-2032.awsdns-62.co.uk, ns-369.awsdns-46.com, ns-602.awsdns-11.net
DNSSEC Not enabled
Hosting
IP Address 141.193.213.10
ASN AS209242 (CLOUDFLARESPECTRUM - Cloudflare London, LLC, US)
Provider Cloudflare
Data source: rdap (0.8s)

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 113 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
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.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
108 ms
Total Time Total request time from DNS lookup through full response.
113 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 64 ms Content Transfer 5 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: MAD)
Got: cf-ray: a23eef15d8d7aa05-MAD
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: a23eef15d8d7aa05-MAD
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 3 header(s)
Got: age=550, cf-cache-status=HIT, x-cache=HIT: 1
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback