Skip to content
https://theknot.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

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

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

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 No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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
A+
DNS Records
1 A records, 78 ms lookup
PASS
1 A records, 78 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 2.16.39.130
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:e0:4bc::2361, 2a02:26f0:e0:4ab::2361
Info::
6 nameserver(s) configured
Got: a3-66.akam.net, a1-32.akam.net, a20-64.akam.net, a11-67.akam.net, a18-66.akam.net, a2-64.akam.net
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: 78 ms
Got: 78 ms
A2.16.39.130
AAAA2a02:26f0:e0:4bc::2361, 2a02:26f0:e0:4ab::2361
CNAME
NSa3-66.akam.net, a1-32.akam.net, a20-64.akam.net, a11-67.akam.net, a18-66.akam.net, a2-64.akam.net
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx3.googlemail.com
30 aspmx2.googlemail.com
TXT
google-site-verification=k3q-KJxrP8qu0xsH2YH56JNzjt3U8uRH5QtsBDrTE4U
_globalsign-domain-verification=KUVkWrTXATb8IZui5dqoh7JPjKePTjQDpt9xtPADDo
tiktok-developers-site-verification=gx4CnlEMeEnwFbIR6pEV08YorWofe9Zb
vbQYjqTXH24GFmb2LQXodGvAVVENmumxJPdGI9w-9ic
_globalsign-domain-verification=yykX0BEfZyNaTQIOQm-yPH9zT0bzt7ugvs4O3pj0Iy
google-site-verification=pIgohE4mIO2NlhSaDINin4sWCJdShujyOFUyYVpcNPU
apple-domain-verification=HZVdu9RLbXK8AolR
google-site-verification=lC6uM3Dtwmja0lUuEcedH7cb4kJzlXlSfpTTgAhnXW8
SPF v=spf1 include:_s00609289.autospf.email ~all
MS=ms36611250
facebook-domain-verification=gjz6w2bqe6zw8h0dbtsf8r5vd6lgs6
google-site-verification=t2sM811k9fxaLg9klWJxaaC5_tH0f7qc01jQBu83Fc0
89vy5y5ryczpb8n0dhl2m80qxqsklcr3
facebook-domain-verification=46k4zco5a6a3a08tdjbz0tg
mixpanel-domain-verify=2a678457-39c5-49c8-b98f-a923ced613d1
google-site-verification=pPCcb85Lj0Mg3NZmg6B8C3TgiwlSvPgLU4I6gpsvbCg
pardot1014932=c4680daba93844fd27aea92930ccc2db0cf4890e119f3a8cdc018ecca85966fa
1password-site-verification=VW5EZBXW5BDGXP3A2AYEDTJGOA
google-site-verification=wc3BSA09dv0Mb6svfUZnKQFK4WlOgLhFYzBWqMR81pM
gv108l1vcy22gvqh9nct1jp8913h9ss3
google-site-verification=K-QFn2Kp5KKdY2ya5hGppYYs3PahzgYEvZ7tM_QFavw
CAALookup not available with standard resolver
Resolved in 78 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

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
1 redirect(s), 60 ms total
PASS
1 redirect(s), 60 ms total
Info::
Single redirect
Got: https://theknot.com → https://www.theknot.com/ (301)
Info::
WWW normalization redirect

https://theknot.com

11 ms · HTTP/1.1

301

https://www.theknot.com/

48 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://theknot.com30111 msHTTP/1.1
2https://www.theknot.com/40348 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:e0:4bc::2361, 2a02:26f0:e0:4ab::2361
Got: 0 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:e0:4bc::2361, 2a02:26f0:e0:4ab::2361 Connection Reachable (0 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.theknot.com/
200https://theknot.com/

HTTP → HTTPS

301http://theknot.com/ https://www.theknot.com/

Consistent

A
Domain Intelligence
theknot.com — via GoDaddy.com, LLC, 30 years, 3 months old
PASS
theknot.com — via GoDaddy.com, LLC, 30 years, 3 months old
Warning::
Domain expires in 63 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 24, 2026
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

8 days

June 24, 2026

SSL certificate

77 days

Issued by DigiCert Inc

Domain age

30 years, 3 months

Registered June 25, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:e0:4ab::2361

Registrar

GoDaddy.com, LLC

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created June 25, 1996 (30 years, 3 months ago)
Expires June 24, 2026 (2 months)
Last Updated June 24, 2025
Name Servers a1-32.akam.net, a11-67.akam.net, a18-66.akam.net, a2-64.akam.net, a20-64.akam.net, a3-66.akam.net
DNSSEC Not enabled
Hosting
IP Address 2a02:26f0:e0:4ab::2361
Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 49 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 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.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
50 ms
Total Time Total request time from DNS lookup through full response.
50 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 9 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