Skip to content
https://generatepress.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
99
GRADE
A+
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
52 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

52
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
A+
DNS Records
2 A records, 38 ms lookup
PASS
2 A records, 38 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.16.150.108, 104.16.151.108
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6810:976c, 2606:4700::6810:966c
Info::
2 nameserver(s) configured
Got: jade.ns.cloudflare.com, marek.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 38 ms
Got: 38 ms
A104.16.150.108, 104.16.151.108
AAAA2606:4700::6810:976c, 2606:4700::6810:966c
CNAME
NSjade.ns.cloudflare.com, marek.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
ca3-1ffdcc808c104fe89ebdd70e8a6bcfbe
ca3-103fe71f8dd849aca56b56bc6a36f0f4
SPF v=spf1 include:_spf.google.com include:mailgun.org ~all
CAALookup not available with standard resolver
Resolved in 38 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://generatepress.com

https://generatepress.com

75 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://generatepress.com20075 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6810:976c, 2606:4700::6810:966c
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6810:976c, 2606:4700::6810:966c Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 252 URLs
PASS
robots.txt present, sitemap with 252 URLs
Info::
robots.txt is present
Got: 141 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 252 entries
Info::
Sitemap index with 252 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 141 B Sitemaps referenced 0 User-agents Googlebot, Bingbot, * Blocking No — crawling allowed
User-agent: Googlebot
Crawl-delay: 10

User-agent: Bingbot
Crawl-delay: 10

User-agent: *
Disallow: /wp-admin/admin-ajax.php
Crawl-delay: 10

sitemap.xml 200 OK
Type Sitemap Index URLs 252 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://generatepress.com/ https://generatepress.com/

Consistent

A+
Domain Intelligence
generatepress.com — via GoDaddy.com, LLC, 12 years, 2 months old
PASS
generatepress.com — via GoDaddy.com, LLC, 12 years, 2 months old
Info::
Domain registered until Apr 11, 2028 (2 years 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

666 days

April 11, 2028

SSL certificate

52 days

Issued by Google Trust Services

Domain age

12 years, 2 months

Registered April 11, 2014

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6810:966c

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 April 11, 2014 (12 years, 2 months ago)
Expires April 11, 2028 (2 years)
Last Updated April 8, 2026
Name Servers jade.ns.cloudflare.com, marek.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6810:966c
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 30 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 41 ms Content Transfer 2 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9efea9671a7e7019-CDG
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9efea9671a7e7019-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback