Digital exposure report
freshdesk.com
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-19 02:55 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS freshdesk.com
- 2.
Limit what your site shares when visitors click links
This reduces how much page address detail is passed to other websites.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://freshdesk.com/ | grep -i "Referrer-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- freshdesk.com
- Website request
- GET https://freshdesk.com/ → https://www.freshworks.com/freshdesk/
- Scan time
- 2026-11-19 02:55:39 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 30/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 22/30 | Some browser protections are missing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDNSSEC — signed DNS records · Hardening gap+7
- 2.LowReferrer-Policy · Hardening gap+3
- 3.LowPermissions-Policy · Hardening gap+2
- 4.LowCSP — protection from script injection · Hardening gap+3
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 2 of the 10 allowed DNS lookups.
v=spf1 include:sendgrid.net include:_spf.google.com -all
$ dig +short TXT freshdesk.com
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; rua=mailto:dmarc-fd-reports@freshworks.com,mailto:dmarc_agg@dmarc.everest.email; ruf=mailto:dmarc-fd-reports@freshworks.com,mailto:dmarc_fr@dmarc.everest.email
$ dig +short TXT _dmarc.freshdesk.com
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: google, k1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCza6QIpOcf8KaRkkKTIriIDWukROqYmaFZ… k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i8… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAp08WVTTpV1kJQI0GlA8Z7bzXd2Jqexy9… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDMUDqXrXoWQCET9/7NQq089SqxmLR0+NF1tTw3…
$ dig +short TXT google._domainkey.freshdesk.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
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
$ dig +short MX freshdesk.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://freshdesk.com/ returned HTTP 200 (final URL: https://www.freshworks.com/freshdesk/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.freshworks.com/freshdesk/
$ curl -sIL https://freshdesk.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://freshdesk.com/
HTTP 301 Location: https://freshdesk.com/
$ curl -sI http://freshdesk.com/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. No matching certificate details were available from CT logs; run the verify command to see the served certificate's dates.
Live TLS handshake: certificate accepted The CT log service was unavailable at the time of the check Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect freshdesk.com:443 -servername freshdesk.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains
$ curl -sIL https://freshdesk.com/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: no script-src/default-src — weakens XSS protection.
Content-Security-Policy: frame-ancestors 'self' *.freshworks.com *.freshdesk.com *.freshservice.com *.myfreshworks.com *.freshcaller.com *.freshteam.com *.freshchat.com *.freshping.io *.freshrelease.com *.freshstatus.io *.freshsuccess.com *.freshsuccess.io views.paperflite.com app.paperflite.com web.paperflite.com canvas.paperflite.com *.optimizely.com *.freshpo.com *.myfreshworks.dev *.freshscout.com freshworks.pathfactory.com *.freshrobust.com *.freshitops.com *.freshcmdb.com *.freshstatusok.com *.firehydrant.io
$ curl -sIL https://freshdesk.com/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: allow-from https://www.freshworks.com frame-ancestors 'self' *.freshworks.com *.freshdesk.com *.freshservice.com *.myfreshworks.com *.freshcaller.com *.freshteam.com *.freshchat.com *.freshping.io *.freshrelease.com *.freshstatus.io *.freshsuccess.com *.freshsuccess.io views.paperflite.com app.paperflite.com web.paperflite.com canvas.paperflite.com *.optimizely.com *.freshpo.com *.myfreshworks.dev *.freshscout.com freshworks.pathfactory.com *.freshrobust.com *.freshitops.com *.freshcmdb.com *.freshstatusok.com *.firehydrant.io
X-Frame-Options: allow-from https://www.freshworks.com CSP frame-ancestors: 'self' *.freshworks.com *.freshdesk.com *.freshservice.com *.myfreshworks.com *.freshcaller.com *.freshteam.com *.freshchat.com *.freshping.io *.freshrelease.com *.freshstatus.io *.freshsuccess.com *.freshsuccess.io views.paperflite.com app.paperflite.com web.paperflite.com canvas.paperflite.com *.optimizely.com *.freshpo.com *.myfreshworks.dev *.freshscout.com freshworks.pathfactory.com *.freshrobust.com *.freshitops.com *.freshcmdb.com *.freshstatusok.com *.firehydrant.io
$ curl -sIL https://freshdesk.com/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://freshdesk.com/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://freshdesk.com/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://freshdesk.com/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://freshdesk.com/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS freshdesk.com: NODATA
$ dig +short DS freshdesk.com
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec freshdesk.com SOA delv freshdesk.com
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "amazontrust.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issuewild "amazontrust.com" | 0 issuewild "pki.goog"
0 issue "amazontrust.com" 0 issue "digicert.com" 0 issue "letsencrypt.org" 0 issue "pki.goog" 0 issuewild "amazontrust.com" 0 issuewild "pki.goog"
$ dig +short CAA freshdesk.com
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
4 NS servers.
ns-1270.awsdns-30.org ns-1955.awsdns-52.co.uk ns-350.awsdns-43.com ns-514.awsdns-00.net
$ dig +short NS freshdesk.com
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rulesNo gaps observed
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline1 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | freshdesk.com | 3.170.51.117 | 3.170.51.30 | 3.170.51.7 | 3.170.51.104 |
| AAAA | freshdesk.com | — |
| MX | freshdesk.com | 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 |
| NS | freshdesk.com | ns-1270.awsdns-30.org | ns-1955.awsdns-52.co.uk | ns-350.awsdns-43.com | ns-514.awsdns-00.net |
| TXT | freshdesk.com | MS=0C0ECA0DED4FEA38DD91BD7C963FF3E1149B19E5 | MS=ms20153233 | facebook-domain-verification=66objfbfqci42q91b05p0mbinby04v | google-site-verification=7osy61fdLAB2qqoS6RpI3XXjbMY2H1fUZRNQtr_5u1w | google-site-verification=R8zDF9qsqup4qkQ6JEATQFelFWhCw_DL_0v57AjDW2s | google-site-verification=r7U0cO3JCFcWuV6Fv0Gr3ecTCAwDTfSsBettTN6XDT0 | google-site-verification=tl7HPJBPcTjmTQLGYGadzLUO6Rx8OzHcjZsP9aVu5NM | include:status-page-domain-verification=db7d1v5mn16h | rovag_verification_token=A3093FB681144F4C83F66823EB95C0F5 | v=spf1 include:sendgrid.net include:_spf.google.com -all |
| TXT | _dmarc.freshdesk.com | v=DMARC1; p=reject; rua=mailto:dmarc-fd-reports@freshworks.com,mailto:dmarc_agg@dmarc.everest.email; ruf=mailto:dmarc-fd-reports@freshworks.com,mailto:dmarc_fr@dmarc.everest.email |
| CAA | freshdesk.com | 0 issue "amazontrust.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issuewild "amazontrust.com" | 0 issuewild "pki.goog" |
| DS | freshdesk.com | — |