Digital exposure report
jenkins.io
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.
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://jenkins.io/ | grep -i "Content-Security-Policy"
- 2.
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 jenkins.io
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- jenkins.io
- Website request
- GET https://jenkins.io/ → https://www.jenkins.io/
- Scan time
- 2026-11-19 02:55:52 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 | 13/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.MediumHSTS — enforce encryption in the browser · Hardening gap+4
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.MediumCSP — protection from script injection · Hardening gap+8
- 4.LowReferrer-Policy · Hardening gap+3
- 5.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:mailgun.org include:sendgrid.net include:_spf.google.com ~all
$ dig +short TXT jenkins.io
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; pct=100;rua=mailto:jenkins-dmarc@olblak.com
$ dig +short TXT _dmarc.jenkins.io
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=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAndtiZ1rUbyB7hGPDdStnxiT5i2ttqEHa… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeUnc9m1vMPyy/LUGw7saeE7dReVktlSNJsWHb…
$ dig +short TXT s1._domainkey.jenkins.io
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mxb.mailgun.org 10 mxa.mailgun.org
$ dig +short MX jenkins.io
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://jenkins.io/ returned HTTP 200 (final URL: https://www.jenkins.io/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.jenkins.io/
$ curl -sIL https://jenkins.io/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 308 → https://jenkins.io
HTTP 308 Location: https://jenkins.io
$ curl -sI http://jenkins.io/ | 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 jenkins.io:443 -servername jenkins.io 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Needs attention · Severity: Medium · Hardening gap · 4/8Encryption enforcement is set for too short a time.
max-age=86400 (1 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=86400; includeSubDomains; preload
$ curl -sIL https://jenkins.io/ | 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://jenkins.io/ | 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: DENY
X-Frame-Options: DENY
$ curl -sIL https://jenkins.io/ | 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://jenkins.io/ | 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://jenkins.io/ | 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://jenkins.io/ | 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://jenkins.io/ | 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 jenkins.io: NODATA
$ dig +short DS jenkins.io
- 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 jenkins.io SOA delv jenkins.io
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 "digicert.com; cansignhttpexchanges=yes" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issue "globalsign.com" | 0 issue "sectigo.com"
0 issue "amazon.com" 0 issue "digicert.com; cansignhttpexchanges=yes" 0 issue "godaddy.com" 0 issue "letsencrypt.org" 0 issue "pki.goog; cansignhttpexchanges=yes" 0 issue "globalsign.com" 0 issue "sectigo.com"
$ dig +short CAA jenkins.io
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.
ns1-06.azure-dns.com ns2-06.azure-dns.net ns3-06.azure-dns.org ns4-06.azure-dns.info
$ dig +short NS jenkins.io
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 diligence2 observed gaps
- SOC 2 / ISO 27001 baseline2 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 | jenkins.io | 128.24.70.119 |
| AAAA | jenkins.io | 2603:1030:408:3::2bd |
| MX | jenkins.io | 10 mxb.mailgun.org | 10 mxa.mailgun.org |
| NS | jenkins.io | ns1-06.azure-dns.com | ns2-06.azure-dns.net | ns3-06.azure-dns.org | ns4-06.azure-dns.info |
| TXT | jenkins.io | jetbrains-domain-verification=9memu05gp112di1q7gijggppf | libera-MjLnxZ2KPqJJnJr6X4WFovAe | _globalsign-domain-verification=b1pmSjP4FyG8hkZunkD3Aoz8tK0FWCje80-YwtLeDU | v=spf1 include:mailgun.org include:sendgrid.net include:_spf.google.com ~all | google-site-verification=4Z81CA6VzprPWEbGFtNbJwWoZBTGmTp3dk7N0hbt87U |
| TXT | _dmarc.jenkins.io | v=DMARC1; p=reject; pct=100;rua=mailto:jenkins-dmarc@olblak.com |
| CAA | jenkins.io | 0 issue "amazon.com" | 0 issue "digicert.com; cansignhttpexchanges=yes" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issue "globalsign.com" | 0 issue "sectigo.com" |
| DS | jenkins.io | — |