Skip to content
https://symantec.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
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
Redirect Chain
2 redirect(s), 725 ms total
REVIEW
2 redirect(s), 725 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::
Redirect overhead: 725 ms total
Got: 725 ms
Info::
Cross-domain redirect detected

https://symantec.com

639 ms · HTTP/1.1

301

https://www.broadcom.com/products/cyber-...

37 ms · HTTP/1.1

301

https://www.broadcom.com/products/cybers...

48 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://symantec.com301639 msHTTP/1.1Apache
2https://www.broadcom.com/products/cyber-...30137 msHTTP/1.1cloudflare
3https://www.broadcom.com/products/cybers...20048 msHTTP/1.1cloudflare

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

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
333 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

333
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
3 A records, 6 ms lookup
PASS
3 A records, 6 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 54.68.22.26, 50.112.202.115, 52.13.171.212
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: edns161.ultradns.biz, edns161.ultradns.com, edns161.ultradns.net, edns161.ultradns.org
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: 6 ms
Got: 6 ms
A54.68.22.26, 50.112.202.115, 52.13.171.212
AAAA
CNAME
NSedns161.ultradns.biz, edns161.ultradns.com, edns161.ultradns.net, edns161.ultradns.org
MX
10 cluster4.us.messagelabs.com
20 cluster4a.us.messagelabs.com
TXT
MS=ms60535775
_16z8h910stop7mt7ar3zrl3sn14y4fp
_20zfrb0yk6lmjc2livuuktnoistv6v1
_8kpqjqkzzq7je7li140uo0t7jy9l3t3
v8wgxyg0n89xxphzccu9ukr9dl2askfo
status-page-domain-verification=k9f7l7gs398h
Sendinblue-code:6c205b4c91f2da07b2f8541b430ca1c9
adobe-idp-site-verification=8022848c-a25c-46e0-84ea-04e5855d848d
dtm-domain-verification=iQ26XU_RJ17ulsIrwwQ-_gJjMFtupKj6DXjW5gV1p2k
google-site-verification=9Dq623Il-GRE1vWUhuSuMeTj0LFiKpvidqPENVg2iS8
google-site-verification=zap4gJQ1F7J0cs9UEmmxTKTQFH8l7msOibEXZ2IoQgM
NgMBOTfcyI1ypf/2w9WVJcWDTTaGuW3WKm070F80pLKJu8KKFPwDwFrMjdflHkDR9V4QQt9CFKCs9Yaj...
vnUJHFSFWwFL67USDl5319B+ITnRVemAfJmrU5l0tEPKVHQkQnvAFsvJZEtNiAJJTWpLu4XTAXX6uehA...
Dynatrace-site-verification=94cafb09-98b8-4fd3-b1be-1f4895f54695__798bsbg1c76qsu...
SPF v=spf1 include:symantec.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._s...
CAALookup not available with standard resolver
Resolved in 6 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
no robots.txt, sitemap with 8 URLs
PASS
no robots.txt, sitemap with 8 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries

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

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.

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

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

Preferred variant: non-www

HTTP → HTTPS

301http://symantec.com/ https://www.broadcom.com/products/cyber-security

Consistent

A+
Domain Intelligence
symantec.com — via CSC Corporate Domains, Inc., 33 years, 10 months old, hosted on AWS
PASS
symantec.com — via CSC Corporate Domains, Inc., 33 years, 10 months old, hosted on AWS
Info::
Domain registered until Nov 23, 2026 (7 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: CSC Corporate Domains, Inc.
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

130 days

November 23, 2026

SSL certificate

333 days

Issued by DigiCert Inc

Domain age

33 years, 10 months

Registered November 24, 1992

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

50.112.202.115

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 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 CSC Corporate Domains, Inc.
Created November 24, 1992 (33 years, 10 months ago)
Expires November 23, 2026 (7 months)
Last Updated March 7, 2024
Name Servers edns161.ultradns.biz, edns161.ultradns.com, edns161.ultradns.net, edns161.ultradns.org
DNSSEC Not enabled
Hosting
IP Address 50.112.202.115
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 157 ms TLS Handshake 318 ms Server Processing 158 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