Digital exposure report
sendgrid.com
High exposure. Significant weaknesses put the brand, customers and email at risk.
Scanned: 2026-11-19 05:57 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell browsers to always use the secure version
Helps browsers use HTTPS on future visits after they have received the policy.
Who can fix it: Your web host
How to verify after the fix
curl -sIL https://sendgrid.com/ | grep -i "Strict-Transport-Security"
- 2.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://sendgrid.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- sendgrid.com
- Website request
- GET https://sendgrid.com/ → https://www.twilio.com/en-us/sendgrid
- Scan time
- 2026-11-19 05:57:58 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 | 29/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 | 0/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 2.MediumClickjacking protection · Hardening gap+5
- 3.MediumDNSSEC — signed DNS records · Hardening gap+7
- 4.MediumCSP — protection from script injection · Hardening gap+8
- 5.LowX-Content-Type-Options · Hardening gap+4
- 6.LowReferrer-Policy · Hardening gap+3
- 7.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 3 of 10 DNS lookups.
v=spf1 include:sendgrid.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:stspg-customer.com ip4:167.89.60.95 ip4:50.31.36.205 ~all$ dig +short TXT sendgrid.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; sp=reject; pct=100; adkim=r; aspf=r; rua=mailto:dmarc_agg@vali.email,mailto:dmarc_rua@sendgrid.com; ruf=mailto:dmarc@sendgrid.com; fo=1; rf=afrf; ri=86400
$ dig +short TXT _dmarc.sendgrid.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: s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2LaY8C3pdtdkSF6C+TTYw0bIKAHt70oF… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQChUpCk6itlhr2WBAtmfviFFznp4W3uvrOwFost…
$ dig +short TXT s1._domainkey.sendgrid.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
1 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
0 smtp.google.com
$ dig +short MX sendgrid.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://sendgrid.com/ returned HTTP 200 (final URL: https://www.twilio.com/en-us/sendgrid). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.twilio.com/en-us/sendgrid
$ curl -sIL https://sendgrid.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://sendgrid.com/
HTTP 301 Location: https://sendgrid.com/
$ curl -sI http://sendgrid.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. Latest issuance in CT logs: GoDaddy, expiring 2027-02-28 (101 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: GoDaddy Valid from: 2026-02-06 Valid until: 2027-02-28 Names: *.sendgrid.com, sendgrid.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect sendgrid.com:443 -servername sendgrid.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Failed · Severity: High · Hardening gap · 0/8Browsers aren't told to always use an encrypted connection, enabling interception attacks on public networks.
No Strict-Transport-Security header. Users are exposed to SSL stripping on the first request.
Strict-Transport-Security: (missing)
$ curl -sIL https://sendgrid.com/ | grep -i "Strict-Transport-Security"
- Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
- Gradually raise it to 31536000 (one year) and add includeSubDomains.
- Consider preload only once the policy is stable — removal from the preload list is slow.
/* Strict-Transport-Security: max-age=31536000; includeSubDomains
Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.
CSP — protection from script injection
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://sendgrid.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
Failed · Severity: Medium · Hardening gap · 0/5Missing X-Frame-Options / frame-ancestors: this removes one layer of protection against clickjacking.
No valid X-Frame-Options and no frame-ancestors in the CSP.
X-Frame-Options: (missing)
$ curl -sIL https://sendgrid.com/ | grep -i "X-Frame-Options"
- Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
- Also set frame-ancestors in the CSP — the modern alternative.
/* X-Frame-Options: SAMEORIGIN
Safety: This change is made in your server/CDN settings. Test on staging before production. If partners embed the site in an iframe, add them to frame-ancestors instead of using DENY.
X-Content-Type-Options
Failed · Severity: Low · Hardening gap · 0/4The browser may interpret files as code unintentionally.
Missing X-Content-Type-Options: nosniff header (MIME sniffing).
X-Content-Type-Options: (missing)
$ curl -sIL https://sendgrid.com/ | grep -i "X-Content-Type-Options"
- Add X-Content-Type-Options: nosniff to every response.
/* X-Content-Type-Options: nosniff
Safety: This change is made in your server/CDN settings. Test on staging before production.
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://sendgrid.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://sendgrid.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://sendgrid.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 sendgrid.com: NODATA
$ dig +short DS sendgrid.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 sendgrid.com SOA delv sendgrid.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 "amazon.com" | 0 issue "globalsign.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "sectigo.com" | 0 issue "symantec.com"
0 issue "amazon.com" 0 issue "globalsign.com" 0 issue "godaddy.com" 0 issue "letsencrypt.org" 0 issue "sectigo.com" 0 issue "symantec.com"
$ dig +short CAA sendgrid.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-1389.awsdns-45.org ns-2039.awsdns-62.co.uk ns-506.awsdns-63.com ns-697.awsdns-23.net
$ dig +short NS sendgrid.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.03 observed gaps
- NIS2 / vendor due diligence2 observed gaps
- SOC 2 / ISO 27001 baseline4 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 | sendgrid.com | 3.142.214.154 | 18.217.167.55 | 54.237.12.3 | 54.243.224.74 | 44.209.50.213 | 3.136.127.8 | 18.189.137.195 | 52.2.178.113 |
| AAAA | sendgrid.com | — |
| MX | sendgrid.com | 0 smtp.google.com |
| NS | sendgrid.com | ns-1389.awsdns-45.org | ns-2039.awsdns-62.co.uk | ns-506.awsdns-63.com | ns-697.awsdns-23.net |
| TXT | sendgrid.com | 48ed3283-0038-4458-8cb0-d2e7d0a4b860 | 8mqpm5f9vltr3jvue71slj2j31 | MS=ms77173225 | anthropic-domain-verification-gjxs4q=b0anOdwQdQOCAOZGbpSFZUrIz | dcacl5d6qbb453nflucim3hi48 | efd3d1covh2tjg32cohdkjof71 | facebook-domain-verification=dfv1zm6tx7ues6olt99mpc58vh49qj | facebook-domain-verification=jotjcwyly7se4q6c3xsysztxo287s9 | google-site-verification=-BR0U2prX8YJz74uUQygVn22zPdt86Jc5FVd5ZX6xXo | google-site-verification=gZJHxa9fylVS3VZ3Zl8jPTZesFDJi28bh5PQJujhez8 | knp3gmub9ht14m0lg24j0e5rq1 | loaderio=dc99536e3eb902ffc82885541e224e7c | ms2jsau3o1f4h802lr68bsb256 | n0mu5saqt0fr95cu201trbacah | postman-domain-verification=06c6947dd936dddbbfe7a7e5a71b5c984a44e5ce0cadd7a8174320c42fd2f5e2f10e18590d5fbaa5f574df473f2a841a8fc6bcb4fed1ec15254845ba5aad1ab1 | status-page-domain-verification=989qbtpx3q0r | v=spf1 include:sendgrid.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:stspg-customer.com ip4:167.89.60.95 ip4:50.31.36.205 ~all |
| TXT | _dmarc.sendgrid.com | v=DMARC1; p=reject; sp=reject; pct=100; adkim=r; aspf=r; rua=mailto:dmarc_agg@vali.email,mailto:dmarc_rua@sendgrid.com; ruf=mailto:dmarc@sendgrid.com; fo=1; rf=afrf; ri=86400 |
| CAA | sendgrid.com | 0 issue "amazon.com" | 0 issue "globalsign.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "sectigo.com" | 0 issue "symantec.com" |
| DS | sendgrid.com | — |