Skip to content
https://www.linode.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
5 PASS 4 REVIEW
B
DNS Records
2 A records, 34 ms lookup
REVIEW
2 A records, 34 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 23.211.15.133, 23.211.15.137
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:e0::211:2548, 2a02:26f0:e0::211:2560
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: linode.com.edgekey.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 34 ms
Got: 34 ms
A23.211.15.133, 23.211.15.137
AAAA2a02:26f0:e0::211:2548, 2a02:26f0:e0::211:2560
CNAMElinode.com.edgekey.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 34 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
HTTP Probe Timing
Total 1484 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 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.
1.48 s
Total Time Total request time from DNS lookup through full response.
1.48 s

Connection waterfall

DNS Lookup 47 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 1.43 s Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
82 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

82
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
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: x-akamai-transformed: 9 161546 0 pmb=mRUM,3
CDN Detected: Akamai
Provider Akamai Evidence x-akamai-transformed: 9 161546 0 pmb=mRUM,3
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.linode.com

https://www.linode.com

1320 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.linode.com2001320 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:e0::211:2548, 2a02:26f0:e0::211:2560
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:e0::211:2548, 2a02:26f0:e0::211:2560 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 499 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 499 B Sitemaps referenced 1 User-agents *, Googlebot Blocking No — crawling allowed
#   You know how to read a robots.txt file.
# What else do you know? Share your knowledge at                              
#     https://www.linode.com/community

User-agent: *
Disallow: /welcome/
Disallow: /library/
Disallow: /docs/search/
Disallow: /docs/topresults/
Disallow: /community/questions/search/ 
Disallow: /search/*/feed
Disallow: /search/*/*

User-agent: Googlebot
Disallow: /wp-content/uploads/*

#User-agent: Yeti
#Disallow: /docs/

Sitemap: https://www.linode.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 8 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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: www

HTTP → HTTPS

301http://www.linode.com/ → https://www.linode.com/

Consistent

A+
Domain Intelligence
linode.com — via MarkMonitor Inc., 23 years, 6 months old
PASS
linode.com — via MarkMonitor Inc., 23 years, 6 months old
Info::
Domain registered until Jan 26, 2027 (9 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: MarkMonitor Inc.
Domain expiry

197 days

January 26, 2027

SSL certificate

82 days

Issued by Let's Encrypt

Domain age

23 years, 6 months

Registered January 26, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:e0::211:2548

Registrar

MarkMonitor Inc.

Lock status unknown 6 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
Registrar MarkMonitor Inc.
Created January 26, 2003 (23 years, 6 months ago)
Expires January 26, 2027 (9 months)
Last Updated April 15, 2024
Name Servers a1-249.akam.net, a12-65.akam.net, a16-64.akam.net, a3-67.akam.net, a4-64.akam.net, a7-65.akam.net
DNSSEC Not enabled
Hosting
IP Address 2a02:26f0:e0::211:2548
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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback