mozilla.org
mozilla.org describes itself as "Mozilla is the not-for-profit behind the lightning fast Firefox browser. We put people over profit to give everyone more power online.". It was registered in 1998, served from Kansas City, United States. It has a valid HTTPS certificate, 5 of 6 common security headers.
What is mozilla.org about?
The words appearing most often on the homepage, excluding common filler, are a rough indication of subject matter rather than a description of the business:
- espa ×5
- cookies ×4
- mozilla ×3
- additional ×3
- english ×3
- improve ×2
- experience ×2
- norsk ×2
- portugu ×2
- sloven ×2
Does mozilla.org publish the usual trust pages?
Found: about, contact, privacy. Not found at the usual addresses: terms. These were checked at conventional paths only, so a site using different URLs may publish them elsewhere.
How does mozilla.org compare with other domains analysed here?
Measured against the 121 domains in this index. This is a small, self-selected sample — the domains people happened to look up — not a representative sample of the web.
| Response time | Faster than 81% of them (median 790ms) |
|---|---|
| Security headers | More than 95% of them |
| Domain age | Older than 97% of them |
Related domains in this index
Other analysed domains served from the same country:
- stackoverflow.com
- vercel.com
- jsonapi.org
- theinstanavigation.com
- coatnews.com
- kextra.com
- newsgiga.com
- storkworld.com
When was mozilla.org registered?
mozilla.org was registered on 24 January 1998, which makes it about 28 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is MarkMonitor Inc..
Registration runs until 23 January 2027.
The domain carries 6 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 24 January 1998 |
|---|---|
| Expires | 23 January 2027 |
| Registrar | MarkMonitor Inc. |
| Registry status | client delete prohibited, server delete prohibited, client transfer prohibited, server transfer prohibited, client update prohibited, server update prohibited |
Where is mozilla.org hosted?
The first address resolves to infrastructure in Kansas City, United States.
The network is operated by Google Cloud (AS396982 Google LLC).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is mozilla.org running on?
No platform, framework or analytics fingerprints were found in the homepage markup of mozilla.org. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 200 over HTTPS.
At 245ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 47KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | granian |
|---|---|
| Compression | gzip |
| Page size | 47,774 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 48 characters, inside the range that displays without truncation.
A meta description of 134 characters is present.
All 11 images on the homepage have alt attributes.
| Title | Internet for people, not profit — Mozilla Global (48 chars) |
|---|---|
| Meta description | Mozilla is the not-for-profit behind the lightning fast Firefox browser. We put people over profit to give everyone more power online. (134 chars) |
| H1 | Choose your language or locale to browse Mozilla.org (1 on the page) |
| Canonical | not set |
| Open Graph title | Internet for people, not profit |
| Headings / images | 25 H2s, 11 images (0 without alt text) |
Is mozilla.org served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is valid until 2026-12-13, which is 69 days from the date of this check. It covers 1 hostname.
- mozilla.org
The certificate has 69 days left to run.
It covers 1 hostname, so it was issued for this site specifically.
Which security headers does it set?
5 of 6 are set (HSTS, Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy). Absent: Permissions-Policy.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31536000 |
| Content Security Policy | yes | form-action 'self' https://abdri3ttkb.execute-api.us-east-2.amazonaws.com https://accounts.firefox.com/ https://basket.m |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | DENY |
| Referrer-Policy | yes | strict-origin-when-cross-origin |
| Permissions-Policy | no | — |
How is DNS configured for mozilla.org?
| IP addresses | 35.190.14.201, 2600:1901::c197:0:0:0:0 |
|---|---|
| Reverse DNS | 201.14.190.35.bc.googleusercontent.com, 2600:1901::c197:0:0:0:0 |
| Name servers | ns4-64.akam.net, ns1-240.akam.net, ns5-65.akam.net, ns7-66.akam.net |
| Mail (MX) | alt1.aspmx.l.google.com (pri 5), aspmx3.googlemail.com (pri 10), alt2.aspmx.l.google.com (pri 5), aspmx.l.google.com (pri 1) |
| SPF | v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:_spf.mozilla.com include:_spf.google.com include:spf.fundraiseup.com ~all |
| TXT records | 17 |
mozilla.org resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 4 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 201.14.190.35.bc.googleusercontent.com, 2600:1901::c197:0:0:0:0, which usually names the hosting provider.
Who runs DNS and mail for mozilla.org?
DNS is operated by Akamai rather than self-hosted name servers.
Mail is handled by Google Workspace.
The domain publishes AAAA records and accepts connections over IPv6.
What else is worth noting about mozilla.org?
12 of 12 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.
1 email address appears in the homepage markup, where address-harvesting crawlers will find it.
What has changed on mozilla.org?
This domain has been checked 2 times. Only checks where something actually moved are recorded, so each row below is a real change rather than a repeat measurement.
| Checked | HTTP | Response | IP | Headers |
|---|---|---|---|---|
| 4 Oct 2026 | 200 | 245ms | 35.190.14.201 | 5/6 |
| 4 Oct 2026 | 200 | 704ms | 35.190.14.201 | 5/6 |
Changes recorded at the most recent check:
- name servers: ns7-66.akam.net,ns5-65.akam.net,ns1-240.akam.net,ns4-64.akam.net → ns4-64.akam.net,ns1-240.akam.net,ns5-65.akam.net,ns7-66.akam.net
- mail servers: aspmx3.googlemail.com (pri 10),aspmx.l.google.com (pri 1),alt2.aspmx.l.google.com (pri 5) → alt1.aspmx.l.google.com (pri 5),aspmx3.googlemail.com (pri 10),alt2.aspmx.l.google.com (pri 5)
- response time: 704ms → 245ms
Can mozilla.org be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
CAA records restrict certificate issuance to 6 named authorities (issue amazon.com, issue certainly.com, issue awstrust.com, iodef mailto:foxsec+caaiodef@mozilla.com), so no other CA should be able to issue for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What else does mozilla.org publish?
A security.txt file is published, giving security researchers a documented way to report vulnerabilities. Very few sites bother.
What does robots.txt allow?
robots.txt is 66 bytes and names 1 user-agent group. It does not blanket-disallow general crawlers.
No sitemap is declared in robots.txt.
AI crawler policy
robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does mozilla.org load from third parties?
The homepage pulls resources from 2 third-party hosts (mastodon.social, transcend-cdn.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
The page links or refers to X/Twitter, LinkedIn, Instagram, YouTube, Mastodon.
Does mozilla.org settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both mozilla.org and www.mozilla.org answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can mozilla.org be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does mozilla.org run?
No analytics or advertising trackers were detected on the homepage of mozilla.org, which is unusual for a commercial site.
How does mozilla.org look when shared?
All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.
The page declares 80 hreflang alternates (x-default, ach, ar, ast, be, bg, br, bs, ca, cak, cs, cy), so it targets more than one language or region.
How are images, fonts and scripts handled?
11 images on the homepage, 10 of them lazy-loaded (91%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 4 external stylesheets and 12 external scripts, with 1 carrying defer or async.
Responses carry Varnish/Fastly edge and edge cache edge headers, so content is served from a CDN rather than straight from the origin.
Is mozilla.org accessible and current?
The page uses 5 landmark elements and 9 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
The visible copyright notice reads 1998, 28 years behind the current year, which usually indicates the site is not actively maintained.
1 deprecated HTML element is still in use (center, font, marquee or blink).
Can search engines index mozilla.org?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
The homepage carries 110 internal and 24 external links across 16 outside hosts.
Visible text makes up 5.5% of the HTML.
How is mozilla.org delivered?
The HTML is served with Cache-Control: max-age=600.
Frequently asked questions
Does mozilla.org set the usual HTTP security headers?
It sets 5 of 6. The ones not present are: Permissions-Policy.
Does mozilla.org allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
Where does this data come from?
Every figure was measured by our own server on 4 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own mozilla.org and want this page removed.
Email hello@quikconsolecom.net from an address at the domain and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026. Analyse another domain →