Skip to content
https://memcached.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
4 PASS 3 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.memcached.org/
200https://memcached.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://memcached.org/

HTTP version does not redirect to HTTPS

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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
HTTP Probe Timing
Total 1169 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
392 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
194 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
389 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.17 s
Total Time Total request time from DNS lookup through full response.
1.17 s

Connection waterfall

DNS Lookup 392 ms TCP Connect 194 ms TLS Handshake 389 ms Server Processing 194 ms Content Transfer 0 ms
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

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 443 ms lookup
PASS
1 A records, 443 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 107.170.231.145
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns4.linode.com, ns5.linode.com, ns1.linode.com, ns2.linode.com, ns3.linode.com
Info::
2 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 (443 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 443 ms
A107.170.231.145
AAAA—
CNAME—
NSns4.linode.com, ns5.linode.com, ns1.linode.com, ns2.linode.com, ns3.linode.com
MX
10 in1-smtp.messagingengine.com
20 in2-smtp.messagingengine.com
TXT
SPF v=spf1 include:spf.messagingengine.com ?all
CAALookup not available with standard resolver
Resolved in 443 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.

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://memcached.org

https://memcached.org

1158 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://memcached.org2001158 msHTTP/1.1nginx/1.10.3
A+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 204 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
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 204 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
#
# To ban all spiders from the entire site uncomment the next two lines:
# User-Agent: *
# Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 14 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
memcached.org — via Gandi SAS, 19 years, 9 months old, hosted on DigitalOcean
PASS
memcached.org — via Gandi SAS, 19 years, 9 months old, hosted on DigitalOcean
Info::
Domain registered until Oct 18, 2028 (2 years, 6 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: 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.
Info::
Hosting: DigitalOcean
Got: AS14061
Domain expiry

855 days

October 18, 2028

SSL certificate

36 days

Issued by Let's Encrypt

Domain age

19 years, 9 months

Registered October 18, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DigitalOcean

ASN AS14061

107.170.231.145

Registrar

Gandi SAS

Unlocked 5 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 Gandi SAS
Created October 18, 2006 (19 years, 9 months ago)
Expires October 18, 2028 (2 years, 6 months)
Last Updated October 22, 2025
Name Servers ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com
DNSSEC Not enabled
Hosting
IP Address 107.170.231.145
ASN AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US)
Provider DigitalOcean
Data source: rdap (2.0s)

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

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

Send Feedback