mozilla.org security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

14risk

Low

Minor observations only.

0Critical

0High

0Medium

21Low

1Info

Collected 23 hours ago4.2sfrom cache

Certificate Transparency448
DNS resolution16
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs45
Registration
DNS posture4
Email authentication2
Certificate
Security headers5
Archived URLs
Analysis22

noteFound 448 hostnames; resolving the first 400.
noteFound 400 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

35.212.137.69 (pulse.mozilla.org) reports rabbitmq 4.2.5, jquery 3.5.1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 35.212.137.69
35.212.221.146 (pulse.mozilla.org) reports rabbitmq 4.2.5, jquery 3.5.1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 35.212.221.146
35.212.157.109 (pulse.mozilla.org) reports jquery 3.5.1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 35.212.157.109
aus4-admin.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: aus4-admin.mozilla.org
snippets-admin.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: snippets-admin.mozilla.org
jenkins.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: jenkins.mozilla.org
jenkins-dxr.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: jenkins-dxr.mozilla.org
dev.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev.mozilla.org
beta.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: beta.mozilla.org
stage.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: stage.mozilla.org
ftp-test.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: ftp-test.mozilla.org
despot-test.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: despot-test.mozilla.org
doctor-test.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: doctor-test.mozilla.org
stage-rsync.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: stage-rsync.mozilla.org
apps-preview.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: apps-preview.mozilla.org
l10n-stage-sj.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: l10n-stage-sj.mozilla.org
beta.developer.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: beta.developer.mozilla.org
api-dev.bugzilla.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: api-dev.bugzilla.mozilla.org
observatory-test.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: observatory-test.mozilla.org
stage.dataviz.data.mozilla.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: stage.dataviz.data.mozilla.org
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: mozilla.org
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: mozilla.org

final https://www.mozilla.org/status 200time 231msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000
✓Content-Security-Policy
style-src 'self' 'unsafe-inline' cdn.transcend.io transcend-cdn.com www.mozilla.org; form-action 'self' https://abdri3ttkb.execute-api.us-east-2.amazonaws.com h…
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 4 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com aspmx.l.google.com aspmx3.googlemail.com
!SPFends in ~all
v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:_spf.mozilla.com include:_spf.google.com include:spf.fundraiseup.com ~all
✓DMARCp=reject
v=DMARC1; p=reject; pct=100; adkim=r; aspf=r; rua=mailto:dmarc_agg@vali.email,mailto:dmarc@mozilla.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issue "letsencrypt.org" · 0 issue "certainly.com" · 0 issue "amazon.com" · 0 iodef "mailto:foxsec+caaiodef@mozilla.com" · 0 issue "sectigo.com" · 0 issue "digicert.com" · 0 issue "amazontrust.com" · 0 issue "awstrust.com" · 0 issue "amazonaws.com" · 0 issue "pki.goog" · 0 issue "comodoca.com"
✓IPv6 (AAAA)
✓4 nameservers
ns1-240.akam.net ns4-64.akam.net ns5-65.akam.net ns7-66.akam.net

✓Registered with MarkMonitor Inc.28.6 years old
mozilla.org
✓Registration expiry138 days
2027-01-23
✓Transfer lock
client delete prohibited, client transfer prohibited, client update prohibited
✓4 nameservers at registry
ns1-240.akam.net ns4-64.akam.net ns5-65.akam.net ns7-66.akam.net

Address	Ports	Edge	Network
141.193.213.11 observatory-test.mozilla.org +2	80443205220532082208320862087+5	Cloudflare~	—
141.193.213.10 observatory-test.mozilla.org +2	80443205220532082208320862087+5	Cloudflare~	—
35.190.14.201 mozilla.org +7	80443	direct	—
34.36.7.128 aus4-admin.mozilla.org +2	80443	direct	—
34.104.33.82 ftp-test.mozilla.org +14	80443	direct	—
151.101.1.91 api-dev.bugzilla.mozilla.org +2	80443	direct	—
151.101.65.91 api-dev.bugzilla.mozilla.org +3	80443	direct	—
151.101.129.91 api-dev.bugzilla.mozilla.org +2	80443	direct	—
151.101.193.91 api-dev.bugzilla.mozilla.org +7	80443	direct	—
35.212.137.69 pulse.mozilla.org +2	4435672	direct	—
35.212.221.146 pulse.mozilla.org +2	4435672	direct	—
35.212.157.109 pulse.mozilla.org +2	443	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

mozilla.org security report

Low

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames