Web sites need to use encryption to help their visitors know they're in the right place, as well as provide confidentiality and content integrity. Sites that don't support HTTPS may expose sensitive data and have their pages modified and subverted.
To deploy HTTPS properly, web sites must redirect all unsafe (plaintext) traffic to the encrypted variant. This approach ensures that no sensitive data is exposed and that further security technologies can be activated.
HTTP Strict Transport Security (HSTS) is an HTTPS extension that instructs browsers to remember sites that use encryption and enforce strict security requirements. Without HSTS, active network attacks are easy to carry out.
HSTS Preloading is informing browsers in advance about a site's use of HSTS, which means that strict security can be enforced even on the first visit. This approach provides best HTTPS security available today.
Content Security Policy (CSP) is an additional security layer that enables web sites to control browser behavior, creating a safety net that can counter attacks such as cross-site scripting.
This host doesn't specify any SMTP servers, which probably means that it doesn't receive email. We are unable to evaluate STARTTLS support, TLS, X.509, and DANE configuration.
The global DNS infrastructure is organized as a series of hierarchical DNS zones. The root zone hosts a number of global and country TLDs, which in turn host further zones that are delegated to their customers. Each organization that controls a zone can delegate parts of its namespace to other zones. In this test we perform detailed inspection of a DNS zone, but only if the host being tested matches the zone.
Nameservers can be referred to by name and by address. In this section we show the names, which can appear in the NS records, the referrals from the parent zone, and the SOA record. In some situations, servers from the parent zone respond authoritatively, in which case we will include them in the list as well.
| Nameserver | Operational | IPv4 | IPv6 | Sources |
|---|---|---|---|---|
| ns-1296.awsdns-34.org. PRIMARY 205.251.197.16 2600:9000:5305:1000::1 | The server is online. | Name resolves to an IPv4 address. | Name resolves to an IPv6 address. | REFERRAL NS SOA |
| ns-1900.awsdns-45.co.uk. 205.251.199.108 2600:9000:5307:6c00::1 | The server is online. | Name resolves to an IPv4 address. | Name resolves to an IPv6 address. | REFERRAL NS |
| ns-374.awsdns-46.com. 205.251.193.118 2600:9000:5301:7600::1 | The server is online. | Name resolves to an IPv4 address. | Name resolves to an IPv6 address. | REFERRAL NS |
| ns-783.awsdns-33.net. 205.251.195.15 2600:9000:5303:f00::1 | The server is online. | Name resolves to an IPv4 address. | Name resolves to an IPv6 address. | REFERRAL NS |
This section shows the configuration of all discovered nameservers by their IP address. To find all applicable nameservers, we inspect the parent zone nameservers for names and glue and then the tested zone nameservers for NS records. We then resolve all discovered names to IP addresses. Finally, we test each address individually.
| Nameserver | Operational | Authoritative | Recursive | UDP | TCP | Sources | Payload Size |
|---|---|---|---|---|---|---|---|
| 205.251.193.118 ns-374.awsdns-46.com. PTR: ns-374.awsdns-46.com. | The server appears to be online. | Nameserver provides authoritative responses | Nameserver doesn't provide recursive service | Nameserver responds to UDP queries | Nameserver responds to TCP queries | NAME | 4096 |
| 205.251.195.15 ns-783.awsdns-33.net. PTR: ns-783.awsdns-33.net. | The server appears to be online. | Nameserver provides authoritative responses | Nameserver doesn't provide recursive service | Nameserver responds to UDP queries | Nameserver responds to TCP queries | NAME | 4096 |
| 205.251.197.16 PRIMARY ns-1296.awsdns-34.org. PTR: ns-1296.awsdns-34.org. | The server appears to be online. | Nameserver provides authoritative responses | Nameserver doesn't provide recursive service | Nameserver responds to UDP queries | Nameserver responds to TCP queries | NAME | 4096 |
| 205.251.199.108 ns-1900.awsdns-45.co.uk. PTR: ns-1900.awsdns-45.co.uk. | The server appears to be online. | Nameserver provides authoritative responses | Nameserver doesn't provide recursive service | Nameserver responds to UDP queries | Nameserver responds to TCP queries | NAME | 4096 |
| 2600:9000:5301:7600::1 ns-374.awsdns-46.com. PTR: ns-374.awsdns-46.com. | The server appears to be online. | Nameserver provides authoritative responses | Nameserver doesn't provide recursive service | Nameserver responds to UDP queries | Nameserver responds to TCP queries | NAME | 4096 |
| 2600:9000:5303:f00::1 ns-783.awsdns-33.net. PTR: ns-783.awsdns-33.net. | The server appears to be online. | Nameserver provides authoritative responses | Nameserver doesn't provide recursive service | Nameserver responds to UDP queries | Nameserver responds to TCP queries | NAME | 4096 |
| 2600:9000:5305:1000::1 PRIMARY ns-1296.awsdns-34.org. PTR: ns-1296.awsdns-34.org. | The server appears to be online. | Nameserver provides authoritative responses | Nameserver doesn't provide recursive service | Nameserver responds to UDP queries | Nameserver responds to TCP queries | NAME | 4096 |
| 2600:9000:5307:6c00::1 ns-1900.awsdns-45.co.uk. PTR: ns-1900.awsdns-45.co.uk. | The server appears to be online. | Nameserver provides authoritative responses | Nameserver doesn't provide recursive service | Nameserver responds to UDP queries | Nameserver responds to TCP queries | NAME | 4096 |
Start of Authority (SOA) records contain administrative information pertaining to one DNS zone, especially the configuration that's used for zone transfers between the primary nameserver and the secondaries. Only one SOA record should exist, with all nameservers providing the same information.
| The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver | ns-1296.awsdns-34.org. |
| Email address of the persons responsible for this zone. Also known as RNAME.Admin email | awsdns-hostmaster.amazon.com. |
| Zone serial or version number.Serial number | 1 |
| The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval | 7,200 seconds (about 2 hours) |
| The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval | 900 seconds (about 15 minutes) |
| The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval | 1,209,600 seconds (about 14 days) |
| TTL for purposes of negative response caching. Negative cache TTL | 86,400 seconds (about 1 day) |
| Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL | 900 seconds (about 15 minutes) |
Below are all DNS queries we submitted during the zone inspection.
| ID | Server | Transport | Question Name | Type | Status |
|---|
Correctly functioning name servers are necessary to hold and distribute information that's necessary for your domain name to operate correctly. Examples include converting names to IP addresses, determining where email should go, and so on. More recently, the DNS is being used to communicate email and other security policies.
These are the results of individual DNS queries against your nameserver for common resource record types.
| Name | TTL | Type | Data |
|---|---|---|---|
| observatory.mozilla.org. | 60 | A | 34.149.1.117 |
| observatory.mozilla.org. | 172800 | NS | ns-1900.awsdns-45.co.uk. |
| observatory.mozilla.org. | 172800 | NS | ns-374.awsdns-46.com. |
| observatory.mozilla.org. | 172800 | NS | ns-783.awsdns-33.net. |
| observatory.mozilla.org. | 172800 | NS | ns-1296.awsdns-34.org. |
| observatory.mozilla.org. | 900 | SOA | ns-1296.awsdns-34.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| observatory.mozilla.org. | 300 | TXT | "What is 34.149.1.117? See https://mozilla-hub.atlassian.net/browse/INFRASEC-133" |
Below are all DNS queries we submitted while inspecting the resource records.
| ID | Server | Question Name | Type | Status |
|---|
DNSSEC is an extension of the DNS protocol that provides cryptographic assurance of the authenticity and integrity of responses; it's intended as a defense against network attackers who are able to manipulate DNS to redirect their victims to servers of their choice. DNSSEC is controversial, with the industry split largely between those who think it's essential and those who believe that it's problematic and unnecessary.
CAA (RFC 8659) is a new standard that allows domain name owners to restrict which CAs are allowed to issue certificates for their domains. This can help to reduce the chance of misissuance, either accidentally or maliciously. In September 2017, CAA became mandatory for CAs to implement.
| The DNS hostname where this policy is located.Policy host | mozilla.org |
| The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue | pki.goog flags: 0 |
| The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue | awstrust.com flags: 0 |
| The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue | sectigo.com flags: 0 |
| The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue | comodoca.com flags: 0 |
| The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue | amazonaws.com flags: 0 |
| The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue | amazon.com flags: 0 |
| The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue | letsencrypt.org flags: 0 |
| The iodef property specifies a means of reporting certificate issue requests or cases of certificate issue for the corresponding domain that violate the security policy of the issuer or the domain name holder.iodef | mailto:foxsec+caaiodef@mozilla.com flags: 0 |
| The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue | amazontrust.com flags: 0 |
| The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue | digicert.com flags: 0 |
An internet hostname can be served by zero or more mail servers, as specified by MX (mail exchange) DNS resource records. Each server can further resolve to multiple IP addresses, for example to handle IPv4 and IPv6 clients. Thus, in practice, hosts that wish to receive email reliably are supported by many endpoint.
Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.
A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.
DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.
Sender Policy Framework (SPF) is a protocol that allows domain name owners to control which internet hosts are allowed to send email on their behalf. This simple mechanism can be used to reduce the effect of email spoofing and cut down on spam.
Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.
| The location from which we obtained this policy.Policy location | _dmarc.mozilla.org |
| DMARC version used by this policy.v | DMARC1 |
| Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p | none |
| Indicates whether strict or relaxed DKIM alignment mode is required.adkim | r |
| Indicates whether strict or relaxed SPF alignment mode is required.aspf | r |
| Addresses to which aggregate feedback is to be sent.rua | mailto:dmarc_agg@vali.email,mailto:dmarc@mozilla.com |
Policy: v=DMARC1; p=none; adkim=r; aspf=r; rua=mailto:dmarc_agg@vali.email,mailto:dmarc@mozilla.com
Host: _dmarc.mozilla.org
Permission record location: mozilla.org._report._dmarc.vali.email
External destination: mailto:dmarc_agg@vali.email
Permission record contents: v=DMARC1;
Permission record location: mozilla.org._report._dmarc.mozilla.com
External destination: mailto:dmarc@mozilla.com
Permission record contents: v=DMARC1;
SMTP Mail Transfer Agent Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections, and to specify whether sending SMTP servers should refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.
SMTP TLS Reporting (RFC 8460), or TLS-RPT for short, describes a reporting mechanism and format by which systems sending email can share statistics and specific information about potential failures with recipient domains. Recipient domains can then use this information to both detect potential attacks and diagnose unintentional misconfigurations. TLS-RPT can be used with DANE or MTA-STS.
To observe your HTTP implementation, we submit a request to the homepage of your site on port 80, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers.
To observe your HTTPS implementation, we submit a request to the homepage of your site on port 443, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers. We use the most recent set of headers returned from the tested hostname for further tests such as HSTS and HPKP.
Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.
| Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols | TLS v1.3 TLS v1.2 TLS v1.1 TLS v1.0 |
| Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference | |
| Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference | Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) |
| Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference | Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA Suite ID: 0xa Cipher name: 3DES (WEAK) Cipher strength: 112 bits Cipher block size: 64 bits (WEAK) Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA 112 bits |
| Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference | Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA Suite ID: 0xa Cipher name: 3DES (WEAK) Cipher strength: 112 bits Cipher block size: 64 bits (WEAK) Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA 112 bits |
| Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference | Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA Suite ID: 0xa Cipher name: 3DES (WEAK) Cipher strength: 112 bits Cipher block size: 64 bits (WEAK) Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA 112 bits |
SCT transports: CERT
SCT transports: CERT
A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.
observatory.mozilla.org | Names | observatory.mozilla.org |
| Subject DN | CN=observatory.mozilla.org |
| Subject Key Identifier | a9d1ec7c979820f903863f065dc2e3a756318c61 |
| Serial | 486b9482a15a5fdd107dde68babe13fa |
| Not Before | 17 Feb 2024 23:42:48 UTC |
| Not After | 18 May 2024 00:38:44 UTC |
| Validity period | 91 days |
| Key Usage | digitalSignature, keyEncipherment | Extended Key Usage | serverAuth |
| Must Staple | No |
| Issuer | |
| Issuer DN | CN=GTS CA 1D4, O=Google Trust Services LLC, C=US |
| Certification Authority | Google Trust Services LLC |
| Validation Type | Domain Validation (DV) |
| Authority Key Identifier | keyid:25e2180eb25791942ae5d45d869083de53b3b892 |
| Parent Certificate | http://pki.goog/repo/certs/gts1d4.der |
| CRL | http://crls.pki.goog/gts1d4/Oum6XtQWsIU.crl |
| OCSP | http://ocsp.pki.goog/s/gts1d4/BTN0zPZVdKE |
| Certificate Transparency | |
| Signed Certificate Timestamps | 18 Feb 2024 00:42:49 UTC | Cloudflare 'Nimbus2024' Log | Qualified 18 Feb 2024 00:42:49 UTC | Google 'Xenon2024' log | Qualified |
| Fingerprints | |
| SHA1 | 663014f10fa5faa8fabe29f3707c4f661556f3c8 |
| SHA256 | 39fb538dedaeb1068ab86da142908d1ddd12fa0e66932fec5fb312d02dfeb5b5 |
| SPKI SHA256 | e25813894c472514ccbad1a4782bcb89ebb7481c316fcedf4ee3f15847b699c6 |
Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.
| Platform | Trusted |
|---|---|
| Apple | |
| Google AOSP | |
| Microsoft | |
| Mozilla |
For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.
| Names | observatory.mozilla.org |
| Subject DN | CN=observatory.mozilla.org |
| Subject Key Identifier | a9d1ec7c979820f903863f065dc2e3a756318c61 |
| Serial | 486b9482a15a5fdd107dde68babe13fa |
| Not Before | 17 Feb 2024 23:42:48 UTC |
| Not After | 18 May 2024 00:38:44 UTC |
| Validity period | 91 days |
| Key Usage | digitalSignature, keyEncipherment | Extended Key Usage | serverAuth |
| Must Staple | No |
| Issuer | |
| Issuer DN | CN=GTS CA 1D4, O=Google Trust Services LLC, C=US |
| Certification Authority | Google Trust Services LLC |
| Validation Type | Domain Validation (DV) |
| Authority Key Identifier | keyid:25e2180eb25791942ae5d45d869083de53b3b892 |
| Parent Certificate | http://pki.goog/repo/certs/gts1d4.der |
| CRL | http://crls.pki.goog/gts1d4/Oum6XtQWsIU.crl |
| OCSP | http://ocsp.pki.goog/s/gts1d4/BTN0zPZVdKE |
| Certificate Transparency | |
| Signed Certificate Timestamps | 18 Feb 2024 00:42:49 UTC | Cloudflare 'Nimbus2024' Log | Qualified 18 Feb 2024 00:42:49 UTC | Google 'Xenon2024' log | Qualified |
| Fingerprints | |
| SHA1 | 663014f10fa5faa8fabe29f3707c4f661556f3c8 |
| SHA256 | 39fb538dedaeb1068ab86da142908d1ddd12fa0e66932fec5fb312d02dfeb5b5 |
| SPKI SHA256 | e25813894c472514ccbad1a4782bcb89ebb7481c316fcedf4ee3f15847b699c6 |
| Subject DN | CN=GTS CA 1D4, O=Google Trust Services LLC, C=US |
| Subject Key Identifier | 25e2180eb25791942ae5d45d869083de53b3b892 |
| Serial | 2008eb2023336658b64cddb9b |
| Not Before | 13 Aug 2020 00:00:42 UTC |
| Not After | 30 Sep 2027 00:00:42 UTC |
| Key Usage | digitalSignature, keyCertSign, cRLSign | Extended Key Usage | serverAuth, clientAuth |
| Issuer | |
| Issuer DN | CN=GTS Root R1, O=Google Trust Services LLC, C=US |
| Certification Authority | Google Trust Services LLC |
| Validation Type | Not Applicable |
| Authority Key Identifier | keyid:e4af2b26711a2b4827852f52662ceff08913713e |
| Parent Certificate | http://pki.goog/repo/certs/gtsr1.der |
| CRL | http://crl.pki.goog/gtsr1/gtsr1.crl |
| OCSP | http://ocsp.pki.goog/gtsr1 |
| CA certificate | Yes (pathlen 0) |
| Fingerprints | |
| SHA1 | 349c385ff8e330f20ead733cd36fb435fee0b403 |
| SHA256 | 64e286b76063602a372efd60cde8db2656a49ee15e84254b3d6eb5fe38f4288b |
| SPKI SHA256 | 7178cf80a7557ba8a88cff2cd18409debb660c51d39d8671718be660616260c1 |
| Subject DN | CN=GTS Root R1, O=Google Trust Services LLC, C=US |
| Subject Key Identifier | e4af2b26711a2b4827852f52662ceff08913713e |
| Serial | 77bd0d6cdb36f91aea210fc4f058d30d |
| Not Before | 19 Jun 2020 00:00:42 UTC |
| Not After | 28 Jan 2028 00:00:42 UTC |
| Key Usage | digitalSignature, keyCertSign, cRLSign |
| Issuer | |
| Issuer DN | CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE |
| Certification Authority | Google Trust Services LLC |
| Validation Type | Not Applicable |
| Authority Key Identifier | keyid:607b661a450d97ca89502f7d04cd34a8fffcfd4b |
| Parent Certificate | http://pki.goog/gsr1/gsr1.crt |
| CRL | http://crl.pki.goog/gsr1/gsr1.crl |
| OCSP | http://ocsp.pki.goog/gsr1 |
| CA certificate | Yes (pathlen unlimited) |
| Fingerprints | |
| SHA1 | 08745487e891c19e3078c1f2a07e452950ef36f6 |
| SHA256 | 3ee0278df71fa3c125c4cd487f01d774694e6fc57e0cd94c24efd769133918e5 |
| SPKI SHA256 | 871a9194f4eed5b312ff40c84c1d524aed2f778bbff25f138cf81f680a7adc67 |
| Subject DN | CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE |
| Subject Key Identifier | 607b661a450d97ca89502f7d04cd34a8fffcfd4b |
| Serial | 20000000000d678b79405 |
| Not Before | 01 Sep 1998 12:00:00 UTC |
| Not After | 28 Jan 2014 12:00:00 UTC (expired 10 years 2 months ago) |
| Key Usage | keyCertSign, cRLSign |
| Issuer | |
| Issuer DN | CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE |
| Certification Authority | Google Trust Services LLC |
| Validation Type | Self-signed |
| CA certificate | Yes (pathlen unlimited) |
| Fingerprints | |
| SHA1 | 2f173f7de99667afa57af80aa2d1b12fac830338 |
| SHA256 | b41b2fbfb93eeab3e0fa6b284adb932cdb3766ed4bc7d14837a8f2d9ae874a23 |
| SPKI SHA256 | 2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64 |
DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.
Cookies are small chunks of text that are sent between your browser and a website. They are often essential to the operation of the site and sometimes contain sensitive information. Session cookies sent from secure sites must be explicitly marked as secure to prevent being obtained by active network attackers.
On virtually all web sites, HTML markup, images, style sheets, JavaScript, and other page resources arrive not only over multiple connections but possibly from multiple servers and sites spread across the entire Internet. For a page to be properly encrypted, it’s necessary that all the content is retrieved over HTTPS. In practice, that’s very often not the case, leading to mixed content security problems.
In this section we look at the security of all embedded resources. Mixed active content occurs when there are unprotected scripts or styles embedded in a page. This is typically not allowed by modern browsers. Mixed passive content (images, videos and such) are typically allowed, but shouldn't be present.
1 script(s) | Status | Link |
|---|---|
| Encrypted | https://observatory.mozilla.org/...86e2ee1ed7c.index.js |
1 CSS file(s) | Status | Link |
|---|---|
| Encrypted | https://observatory.mozilla.org/...6e2ee1ed7c.index.css |
1 media file(s) | Status | Link |
|---|---|
| Encrypted | https://observatory.mozilla.org/...rvatory-wordmark.svg |
Ideally, an encrypted page should only have links that lead to other encrypted pages. If plaintext links are used, passive network attackers can see where people go after they visit your web site. It's also possible that some sensitive information is leaked in the Referer header.
4 link(s) | Status | Link |
|---|---|
| Encrypted | https://developer.mozilla.org/...log/mdn-observatory/ |
| Encrypted | https://github.com/.../httpobs/docs/api.md |
| Encrypted | https://github.com/...observatory-website/ |
| Encrypted | https://github.com/...pobs/docs/scoring.md |
HTTP Strict Transport Security (HSTS) vastly improves security of the network encryption layer. With HSTS enabled, browsers no longer allow clicking through certificate warnings errors, which are typically trivial to exploit. Additionally, they will no longer submit insecure (plaintext) requests to the site in question, even if asked.
| URL from which this policy was obtained.Location | https://observatory.mozilla.org/ |
| Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age | 31,536,000 seconds (about 1 year) |
| When present, this directive forces HSTS activation on allsubdomains. For best security, HSTS should be deployed on the bare domain name (e.g., example.com) and all its subdomains.includeSubDomains | |
| Presence of this directive indicates that a web site wishes to permanently use HSTS and that its policy information should be preloaded (embedded in browsers).preload |
| URL from which this policy was obtained.Location | https://mozilla.org |
| Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age | 60 seconds (about 1 minute) |
| When present, this directive forces HSTS activation on allsubdomains. For best security, HSTS should be deployed on the bare domain name (e.g., example.com) and all its subdomains.includeSubDomains | |
| Presence of this directive indicates that a web site wishes to permanently use HSTS and that its policy information should be preloaded (embedded in browsers).preload |
HTTP Public Key Pinning (HPKP) enables site operators to restrict which certificates are considered valid for their domain names. With a valid HPKP configuration, sites can defeat man in the middle (MITM) attacks using fraudulent or misissued certificates. HPKP is an advanced feature, suitable for use by only high-profile web sites.
Content Security Policy (CSP) is a security mechanism that allows web sites control how browsers process their pages. In essence, sites can restrict what types of resources are loaded and from where. CSP policies can be used to defend against cross-site scripting, prevent mixed content issues, as well as report violations for investigation.
| default-src | 'none' |
| base-uri | - |
| form-action | 'self' |
| connect-src | https://api.ssllabs.com https://hstspreload.org https://http-observatory.security.mozilla.org https://prod.observatory.mdn.prod.webservices.mozgcp.net https://stage.observatory.mdn.nonprod.webservices.mozgcp.net https://securityheaders.com https://sshscan.rubidus.com https://tls.imirhil.fr https://tls-observatory.services.mozilla.com https://www.immuniweb.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com |
| font-src | 'self' |
| frame-ancestors | 'none' |
| img-src | 'self' https://*.google-analytics.com https://*.googletagmanager.com |
| script-src | 'self' https://*.googletagmanager.com |
| style-src | 'self' |
Header: Content-Security-Policy
Value: default-src 'none'; base-uri 'none'; form-action 'self'; connect-src https://api.ssllabs.com https://hstspreload.org https://http-observatory.security.mozilla.org https://prod.observatory.mdn.prod.webservices.mozgcp.net https://stage.observatory.mdn.nonprod.webservices.mozgcp.net https://securityheaders.com https://sshscan.rubidus.com https://tls.imirhil.fr https://tls-observatory.services.mozilla.com https://www.immuniweb.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; font-src 'self'; frame-ancestors 'none'; img-src 'self' https://*.google-analytics.com https://*.googletagmanager.com; script-src 'self' https://*.googletagmanager.com; style-src 'self'
Location: https://observatory.mozilla.org/
Subresource Integrity (SRI) is a new standard that enables browsers to verify the integrity of embedded page resources (e.g., scripts and stylesheets) when they are loaded from third-party web sites. With SRI deployed, remote resources can be used safely, without fear of them being modified by malicious parties.
Expect-CT is a deprecated response HTTP header designed to enable web sites to monitor problems related to their Certificate Transparency (CT) compliance. Should any CT issues arise, browsers that supported this header will submit reports to the specified reporting endpoint. Chrome was the browser that introduced support for this response header, but later deprecated it and removed it in version 107.
The X-Frame-Options header controls page framing, which occurs when a page is incorporated into some other page, possibly on a different site. If framing is allowed, attackers can employ clever tricks to make victims perform arbitrary actions on your site; they do this by showing their web site while forwarding the victim's clicks to yours.
Name: X-Frame-Options
Value: DENY
Some browsers ship with so-called XSS Auditors, built-in defenses against XSS. Although these defenses work against simple reflective XSS attacks, they can be abused by skillful attackers to add weaknesses to otherwise secure web sites. These dangers are present in both filtering and blocking modes. At this time, the Safari browser ships with its XSS defenses enabled by default. For this reason, the best approach is to explicitly disable this functionality.
Name: X-XSS-Protection
Value: 1; mode=block
Some browsers use a technique called content sniffing to override response MIME types provided by HTTP servers and interpret responses as something else (usually HTML). This behavior, which could potentially lead to security issues, should be disabled by attaching an X-Content-Type-Options header to all responses.
Name: X-Content-Type-Options
Value: nosniff
