Skip to content
https://freshdesk.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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
107 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD53-P1)
Got: x-amz-cf-id: l6JO3h9l-ggtK1HWQ5z0CDODom_xBHyM5Q_ZqTxiamr1umwCey_LzA==
Info::
CDN cache status: FunctionGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status FunctionGeneratedResponse from cloudfront Evidence x-amz-cf-id: l6JO3h9l-ggtK1HWQ5z0CDODom_xBHyM5Q_ZqTxiamr1umwCey_LzA==
A+
DNS Records
4 A records, 39 ms lookup
PASS
4 A records, 39 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.154.29.76, 18.154.29.109, 18.154.29.15, 18.154.29.56
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-514.awsdns-00.net, ns-350.awsdns-43.com, ns-1270.awsdns-30.org, ns-1955.awsdns-52.co.uk
Info::
5 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: 39 ms
Got: 39 ms
A18.154.29.76, 18.154.29.109, 18.154.29.15, 18.154.29.56
AAAA
CNAME
NSns-514.awsdns-00.net, ns-350.awsdns-43.com, ns-1270.awsdns-30.org, ns-1955.awsdns-52.co.uk
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 aspmx2.googlemail.com
50 aspmx3.googlemail.com
TXT
google-site-verification=R8zDF9qsqup4qkQ6JEATQFelFWhCw_DL_0v57AjDW2s
google-site-verification=r7U0cO3JCFcWuV6Fv0Gr3ecTCAwDTfSsBettTN6XDT0
google-site-verification=7osy61fdLAB2qqoS6RpI3XXjbMY2H1fUZRNQtr_5u1w
rovag_verification_token=A3093FB681144F4C83F66823EB95C0F5
SPF v=spf1 include:sendgrid.net include:_spf.google.com -all
MS=0C0ECA0DED4FEA38DD91BD7C963FF3E1149B19E5
facebook-domain-verification=66objfbfqci42q91b05p0mbinby04v
MS=ms20153233
google-site-verification=tl7HPJBPcTjmTQLGYGadzLUO6Rx8OzHcjZsP9aVu5NM
include:status-page-domain-verification=db7d1v5mn16h
CAALookup not available with standard resolver
Resolved in 39 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
Redirect Chain
1 redirect(s), 123 ms total
PASS
1 redirect(s), 123 ms total
Info::
Single redirect
Got: https://freshdesk.com → https://www.freshworks.com/freshdesk/ (301)
Info::
WWW normalization redirect
Info::
Cross-domain redirect detected

https://freshdesk.com

14 ms · HTTP/1.1

301

https://www.freshworks.com/freshdesk/

108 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://freshdesk.com30114 msHTTP/1.1CloudFront
2https://www.freshworks.com/freshdesk/200108 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 464 URLs
PASS
robots.txt present, sitemap with 464 URLs
Info::
robots.txt is present
Got: 240 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 464 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 240 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow:

Disallow: */demo-thank-you

Disallow: */thank-you

Disallow: */lp/

Allow: /.well-known/assetlinks.json

Sitemap: https://www.freshworks.com/freshdesk/sitemaps.xml

Sitemap: https://freshdesk.com/sitemaps/index.xml
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.freshdesk.com/
200https://freshdesk.com/

Preferred variant: non-www

HTTP → HTTPS

301http://freshdesk.com/ https://freshdesk.com/

Consistent

A+
Domain Intelligence
freshdesk.com — via NameCheap, Inc., 22 years, 3 months old, hosted on AWS
PASS
freshdesk.com — via NameCheap, Inc., 22 years, 3 months old, hosted on AWS
Info::
Domain registered until May 11, 2027 (1 years 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: NameCheap, 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

303 days

May 11, 2027

SSL certificate

107 days

Issued by Amazon

Domain age

22 years, 3 months

Registered May 11, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.154.29.56

Registrar

NameCheap, 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 NameCheap, Inc.
Created May 11, 2004 (22 years, 3 months ago)
Expires May 11, 2027 (1 years)
Last Updated April 3, 2026
Name Servers ns-1270.awsdns-30.org, ns-1955.awsdns-52.co.uk, ns-350.awsdns-43.com, ns-514.awsdns-00.net
DNSSEC Not enabled
Hosting
IP Address 18.154.29.56
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 36 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
28 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.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
37 ms
Total Time Total request time from DNS lookup through full response.
37 ms

Connection waterfall

DNS Lookup 28 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 4 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