Digital exposure report
pagerduty.com
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-19 02:55 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://pagerduty.com/ | grep -i "Strict-Transport-Security"
- 2.
Stop browsers from guessing file types
This removes one way a file could be treated as something it is not.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://pagerduty.com/ | grep -i "X-Content-Type-Options"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- pagerduty.com
- Website request
- GET https://pagerduty.com/ → https://www.pagerduty.com/
- Scan time
- 2026-11-19 02:55:48 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 | 10/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 15/15 | The domain's infrastructure is well hardened. |
Fix priorities
- 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 2.LowX-Content-Type-Options · Hardening gap+4
- 3.LowReferrer-Policy · Hardening gap+3
- 4.LowPermissions-Policy · Hardening gap+2
- 5.LowCSP — protection from script injection · Hardening gap+3
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:mailgun.org include:pagerduty.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all$ dig +short TXT pagerduty.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_agg@vali.email
$ dig +short TXT _dmarc.pagerduty.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=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuvHD4xSWX+f7le4hI+CPYSqTI8tLyNB3… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCxzpX6J76eH73R3xaNrYf1io0JqPMSLEifrpLI…
$ dig +short TXT s1._domainkey.pagerduty.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 20 alt2.aspmx.l.google.com 30 aspmx2.googlemail.com 30 aspmx3.googlemail.com
$ dig +short MX pagerduty.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://pagerduty.com/ returned HTTP 200 (final URL: https://www.pagerduty.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.pagerduty.com/
$ curl -sIL https://pagerduty.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://pagerduty.com/
HTTP 301 Location: https://pagerduty.com/
$ curl -sI http://pagerduty.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: DigiCert, expiring 2027-03-18 (119 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: DigiCert Valid from: 2026-02-23 Valid until: 2027-03-18 Names: *.pagerduty.com, pagerduty.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect pagerduty.com:443 -servername pagerduty.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://pagerduty.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
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' https://pagerduty.pathfactory.com;
$ curl -sIL https://pagerduty.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.
frame-ancestors 'self' https://pagerduty.pathfactory.com
X-Frame-Options: (missing) CSP frame-ancestors: 'self' https://pagerduty.pathfactory.com
$ curl -sIL https://pagerduty.com/ | grep -i "X-Frame-Options"
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://pagerduty.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://pagerduty.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://pagerduty.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: Next.js
$ curl -sIL https://pagerduty.com/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec pagerduty.com | grep -E "flags:.* ad"
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 iodef "mailto:ssl-tls-certificates-caa-iodef-report.r4785y6f@pdt-circular.pagerduty.com" | 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "comodo.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issuewild "comodo.com" | 0 issuewild "digicert.com"
0 iodef "mailto:ssl-tls-certificates-caa-iodef-report.r4785y6f@pdt-circular.pagerduty.com" 0 issue "amazon.com" 0 issue "amazonaws.com" 0 issue "amazontrust.com" 0 issue "awstrust.com" 0 issue "comodo.com" 0 issue "digicert.com" 0 issue "letsencrypt.org" 0 issue "pki.goog" 0 issuewild "comodo.com" 0 issuewild "digicert.com"
$ dig +short CAA pagerduty.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-474.awsdns-59.com ns-963.awsdns-56.net ns-1285.awsdns-32.org ns-1659.awsdns-15.co.uk
$ dig +short NS pagerduty.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.02 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline3 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 | pagerduty.com | 35.163.146.4 | 44.237.102.140 | 52.36.64.228 |
| AAAA | pagerduty.com | — |
| MX | pagerduty.com | 10 aspmx.l.google.com | 20 alt1.aspmx.l.google.com | 20 alt2.aspmx.l.google.com | 30 aspmx2.googlemail.com | 30 aspmx3.googlemail.com |
| NS | pagerduty.com | ns-474.awsdns-59.com | ns-963.awsdns-56.net | ns-1285.awsdns-32.org | ns-1659.awsdns-15.co.uk |
| TXT | pagerduty.com | DNS monitoring record | 00DE0000000a7oQ=1TBV40000000O7B | asv=b0e9f43059c155b3ecba29c9006475cf | apple-domain-verification=M26BMul1HQfHEYR5 | status-page-domain-verification=g7tgjd7hp622 | docusign=aad4d5eb-97e3-4bbb-aced-8d1f24b3dcc5 | jamf-site-verification=xQCvx9VseZTj325rPxcrOA | cloudhealth=8d48bb09-8b67-42bd-8bd0-722971bfde57 | pendo-domain-verification=5ilh1K4ZyQwkJFYmITgYSr-NASk | amazonses:MzBCFLUEe2G6JdasI22mCosTOM/fvTXWtF430IKC/Kw= | docker-verification=4944e5fa-8cda-4e1a-a36e-73c922f4a150 | cloudflare_dashboard_sso=83f056ce0a3321a1591f9ea0150bde29 | segment-site-verification=XNIAeLc2aqBnXqtPc1QeLaQOQ05xvgIM | cursor-domain-verification-y6fdrf=dPJINl0K6JEpvQ958YNwNBCdy | facebook-domain-verification=dypl8ud5bb7lbw2ujjyjjlbgwsg61r | smartsheet-site-validation=VrJi9ZblneZYi0ATflsMqTTk9byXwYAO | twilio-domain-verification=1eea75e2469b4bd00a3113f11a7c06a0 | bird-domain-verification=a92b8c7d-5d3b-4d07-b86d-eb950a179eae | anthropic-domain-verification-f9z4mn=s19cHKqPQgMK7HRaaCohF9L0f | 27480b40ff5163a9763d6df93174035039a5797d737ccaeab049fd02f1d9c2d6 | google-site-verification=3BxgT12qsg-75RcqXJqeIRdfCoZGZpPoWAUtrsHohzU | google-site-verification=8IObh7yRHj32T08ZYaCuwSO3TUaMrQyu1VPAmPOaSXs | google-site-verification=Q2JLI36_fBOB_Tns7MZdTKRK-BxWl0EmSQq7FXHGQVI | google-site-verification=T0lGuIBgtZW9n5USDTvrLz2bwPIjx7iB1UciRQMo8Z0 | google-site-verification=jIaKcOf0XqQS89HPKVRBFpJEup8jxUSQX9kgiDFBiVM | google-site-verification=rKKcxiHA-2pKQ943sP1BYosFnje8uGqOR_eAhONIbhQ | zoom-domain-verification=ZOOM_verify_924d9e2ae566460faa8a4b5d7b512272 | h1-domain-verification=CHWX6AUg7sg4LA9m38UaBi2wBooc8Wjzr129rpTMu9RuaULG | all-good-technology-inc-domain-verification-7n19ce=PQEY9yGb2LYgDO9xf9yFvW07S | adobe-idp-site-verification=13b2f19835141a22b71e7c0de693fb081c28a671e5b0e68531438cf3dea55d65 | atlassian-domain-verification=7f0nNi0HyfeufsEPkuwHgbli3ZoEijiE2mDchPU+9AtXMsPtyK7vrg041QwpyY+f | parallels-domain-verification=e4a624ed79f440b785992144265e833a88c67d051d3a44eba70e35ac899b0834 | v=spf1 include:mailgun.org include:pagerduty.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all | postman-domain-verification=5d4cdbeac57292a712bfc744928db6733776c07be9260ad1d307df334d26fdc24f8335db09aaf8358a7c4b9a1f07d74593c25b1d3e8d7c5936ec0f82c8fe4c1f |
| TXT | _dmarc.pagerduty.com | v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email |
| CAA | pagerduty.com | 0 iodef "mailto:ssl-tls-certificates-caa-iodef-report.r4785y6f@pdt-circular.pagerduty.com" | 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "comodo.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issuewild "comodo.com" | 0 issuewild "digicert.com" |
| DS | pagerduty.com | 54211 13 2 07f6c70f32f652c7d223fe770b099cf927275807d1bb8231d2bff6e900cbb63b |