Skip to content
https://synology.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 2014 ms total
FIX
2 redirect(s), 2014 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.synology.com:443/
Warning::
Redirect overhead: 2014 ms total
Got: 2014 ms

https://synology.com

418 ms · HTTP/1.1

301

https://www.synology.com:443/

781 ms · HTTP/1.1

302

https://www.synology.com/en-global

816 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://synology.com301418 msHTTP/1.1awselb/2.0
2https://www.synology.com:443/302781 msHTTP/1.1APISIX
3https://www.synology.com/en-global200816 msHTTP/1.1APISIX

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
TLS Certificate Expiry & Recommendations
210 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

210
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 OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 31 ms lookup
PASS
2 A records, 31 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 3.96.38.65, 15.156.123.137
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-498.awsdns-62.com, ns-1064.awsdns-05.org, ns-705.awsdns-24.net, ns-1712.awsdns-22.co.uk
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
Info::
DNS resolution time: 31 ms
Got: 31 ms
A3.96.38.65, 15.156.123.137
AAAA—
CNAME—
NSns-498.awsdns-62.com, ns-1064.awsdns-05.org, ns-705.awsdns-24.net, ns-1712.awsdns-22.co.uk
MX
10 mail.synology.com
20 usmail.synology.com
TXT
google-site-verification=ALTosOMjfqO1e3waISlqUtAWVDPbkd1xTc2zZTecJEI
MS=ms48619058
google-site-verification=JVX3mTh4Tf0UkH7dbWDkRXj2sxVsD9BG5vhu_fme_eE
google-site-verification=2uuWSS-PQu_3wdAfpKznMi8j_LmMJNNxDCo5CQBl-qw
google-site-verification=BbJczAIhIiCLaNKZgHnZmvApYcQ15k3hu1rsrNWFdWs
ZA=zRLoTz+5H4NqLuCfaPj4/w==
google-site-verification=yye3FPh6LcNp7ErWXUcEB7XEMehHrKd3ThjBMmsV7mc
SPF v=spf1 mx:synology.com include:_spf.salesforce.com include:amazonses.com include...
google-site-verification=iZjYDwFil9JWa4480fxaMOv0B0Gn_47rgtpuoRRN-iE
google-site-verification=XrSxJM15m-RvajbL3iwihOg5rO0KKqzKb_48F5Tck54
google-site-verification=vpw-OR-MsiNlWHU3DZRHsOZ_hKvDFg15c4_4uoJnX5c
CAALookup not available with standard resolver
Resolved in 31 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.

A+
Crawlability
robots.txt present, sitemap with 92 URLs
PASS
robots.txt present, sitemap with 92 URLs
Info::
robots.txt is present
Got: 127 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 92 entries
Info::
Sitemap index with 92 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 127 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /*/search$
Disallow: /*/search?$
Disallow: /*/search?q=

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

www / non-www

302https://www.synology.com/
200https://synology.com/

Preferred variant: non-www

HTTP → HTTPS

301http://synology.com/ → https://synology.com:443/

Consistent

A+
Domain Intelligence
synology.com — via GoDaddy.com, LLC, 26 years, 7 months old, hosted on AWS
PASS
synology.com — via GoDaddy.com, LLC, 26 years, 7 months old, hosted on AWS
Info::
Domain registered until Jan 29, 2030 (3 years, 10 months remaining)
Info::
DNSSEC is enabled
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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

1326 days

January 29, 2030

SSL certificate

210 days

Issued by Amazon

Domain age

26 years, 7 months

Registered January 29, 2000

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

15.156.123.137

Registrar

GoDaddy.com, LLC

Unlocked 4 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 GoDaddy.com, LLC
Created January 29, 2000 (26 years, 7 months ago)
Expires January 29, 2030 (3 years, 10 months)
Last Updated April 3, 2024
Name Servers ns-1064.awsdns-05.org, ns-1712.awsdns-22.co.uk, ns-498.awsdns-62.com, ns-705.awsdns-24.net
DNSSEC Enabled
Hosting
IP Address 15.156.123.137
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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 435 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
18 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
103 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
209 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
435 ms
Total Time Total request time from DNS lookup through full response.
435 ms

Connection waterfall

DNS Lookup 18 ms TCP Connect 103 ms TLS Handshake 209 ms Server Processing 105 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