Skip to content
https://samba.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 957 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 957 B Sitemaps referenced 0 User-agents googlebot, ia_archiver, baidu, msnbot, Yandex, ScoutJet, Bingbot, Jeeves, scooter, nutch, openbot, larbin, DuckDuckBot, Teoma Blocking No — crawling allowed
# It is a condition of access to this site that automated retrieval
# agents obey the Robots Exclusion Protocol.  Sites that disobey will
# be banned or subject to other penalties.

User-agent: googlebot
User-agent: ia_archiver
User-agent: scooter
User-agent: nutch
User-agent: openbot
User-agent: baidu
User-agent: larbin
User-agent: msnbot
User-agent: Yandex
User-agent: ScoutJet
User-agent: Bingbot
User-agent: DuckDuckBot
Disallow: /mailman/private/
Disallow: /cgi-bin/
Disallow: /cvsweb/
Disallow: /viewcvs/
Disallow: /ftp

# askjeeves/teoma can't understand records with multiple ua fields.
User-Agent: Jeeves
User-Agent: Teoma
Disallow: /mailman/private/
Disallow: /cgi-bin/
Disallow: /cvsweb/
Disallow: /viewcvs/
Disallow: /ftp

# Disallow everyone else, because some people of limited intelligence
# like to try to mirror everything.  If you are a real search agent and 
# feel you should be an exception, write to us.

#User-agent: *
#Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.samba.org/
200https://samba.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://samba.org/ https://samba.org/

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 41 ms lookup
PASS
1 A records, 41 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 144.76.82.148
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a01:4f8:192:486::2:3
Info::
5 nameserver(s) configured
Got: ns3.he.net, ns5.he.net, ns4.he.net, ns1.samba.org, ns2.he.net
Info::
3 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: 41 ms
Got: 41 ms
A144.76.82.148
AAAA2a01:4f8:192:486::2:3
CNAME
NSns3.he.net, ns5.he.net, ns4.he.net, ns1.samba.org, ns2.he.net
MX
5 ns1.samba.org
7 smtp.samba.org
9 ns1.samba.org
TXT
google-site-verification=VDVaSN4Sj04vJ_X75gzat32kWIO4m4lkdBCzmuGEigE
yahoo-verification-key=s9lNbAHWsrCcWwGJnz6MTiE8rmB2/cTMbM6DkDIqE1I=
SPF v=spf1 ip4:144.76.82.147 ip4:144.76.82.148 ip6:2a01:4f8:192:486::/64 ~all
CAALookup not available with standard resolver
Resolved in 41 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), 232 ms total
PASS
1 redirect(s), 232 ms total
Info::
Single redirect
Got: https://samba.org → https://www.samba.org/ (301)
Info::
WWW normalization redirect

https://samba.org

95 ms · HTTP/1.1

301

https://www.samba.org/

137 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://samba.org30195 msHTTP/1.1
2https://www.samba.org/200137 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (29 ms)
PASS
IPv6 reachable (29 ms)
Info::
IPv6 is configured and reachable at 2a01:4f8:192:486::2:3
Got: 29 ms connect
IPv6 Ready
AAAA Records 2a01:4f8:192:486::2:3 Connection Reachable (29 ms)
A+
Domain Intelligence
samba.org — via Gandi SAS, 28 years, 8 months old
PASS
samba.org — via Gandi SAS, 28 years, 8 months old
Info::
Domain registered until Jan 9, 2027 (8 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Gandi SAS
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

177 days

January 9, 2027

SSL certificate

64 days

Issued by Let's Encrypt

Domain age

28 years, 8 months

Registered January 10, 1998

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a01:4f8:192:486::2:3

Registrar

Gandi SAS

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Gandi SAS
Created January 10, 1998 (28 years, 8 months ago)
Expires January 9, 2027 (8 months)
Last Updated November 15, 2025
Name Servers ns1.samba.org, ns2.he.net, ns3.he.net, ns4.he.net, ns5.he.net
DNSSEC Enabled
Hosting
IP Address 2a01:4f8:192:486::2:3
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 37 ms TCP Connect 29 ms TLS Handshake 33 ms Server Processing 32 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