Skip to content
https://gohugo.io

Infrastructure

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

Certificate validity

36
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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 & Delivery
Netlify
REVIEW
Netlify
Info::
Site is served via Netlify CDN
Got: x-nf-request-id: 01KPRV30EHCST6D020WD34EF59
CDN Detected: Netlify
Provider Netlify Evidence x-nf-request-id: 01KPRV30EHCST6D020WD34EF59
A
DNS Records
2 A records, 278 ms lookup
PASS
2 A records, 278 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 35.157.26.135, 63.176.8.218
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258
Info::
2 nameserver(s) configured
Got: ruth.ns.cloudflare.com, andy.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
Warning::
DNS resolution is slow (278 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 278 ms
A35.157.26.135, 63.176.8.218
AAAA2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258
CNAME—
NSruth.ns.cloudflare.com, andy.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
google-site-verification=uutFIZ2clJ49_5HaqR_dodh8jNMecnjW4MYNYmVdLSQ
SPF v=spf1 include:mailgun.org ~all
CAALookup not available with standard resolver
Resolved in 278 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.

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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://gohugo.io

https://gohugo.io

107 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gohugo.io200107 msHTTP/1.1Netlify
A+
IPv6 Readiness
IPv6 reachable (35 ms)
PASS
IPv6 reachable (35 ms)
Info::
IPv6 is configured and reachable at 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258
Got: 35 ms connect
IPv6 Ready
AAAA Records 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258 Connection Reachable (35 ms)
A
Crawlability
no robots.txt, sitemap with 785 URLs
PASS
no robots.txt, sitemap with 785 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 785 entries

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml 200 OK
Type URL Set URLs 785 entries Valid XML Yes
Sample URLs:
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.gohugo.io/
200https://gohugo.io/

Preferred variant: non-www

HTTP → HTTPS

301http://gohugo.io/ → https://gohugo.io/

Consistent

A+
Domain Intelligence
gohugo.io — via Cloudflare, Inc, 11 years, 9 months old
PASS
gohugo.io — via Cloudflare, Inc, 11 years, 9 months old
Info::
Domain registered until Sep 17, 2026 (4 months remaining)
Info::
Registrar: Cloudflare, Inc
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Domain expiry

95 days

September 17, 2026

SSL certificate

36 days

Issued by Let's Encrypt

Domain age

11 years, 9 months

Registered September 17, 2014

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a05:d014:58f:6200::258

Registrar

Cloudflare, Inc

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar Cloudflare, Inc
Created September 17, 2014 (11 years, 9 months ago)
Expires September 17, 2026 (4 months)
Last Updated August 23, 2025
Name Servers ruth.ns.cloudflare.com, andy.ns.cloudflare.com
Registrant DATA REDACTED
Hosting
IP Address 2a05:d014:58f:6200::258
Data source: whois (0.9s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 184 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
42 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
35 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
36 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
150 ms
Total Time Total request time from DNS lookup through full response.
185 ms

Connection waterfall

DNS Lookup 42 ms TCP Connect 35 ms TLS Handshake 36 ms Server Processing 37 ms Content Transfer 35 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback