DNS Zone

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.

Nameserver Names

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 Addresses

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.

Start of Authority (SOA) Record

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.

Backing DNS Queries

Below are all DNS queries we submitted during the zone inspection.

DNS Records

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.

DNS Records

These are the results of individual DNS queries against your nameserver for common resource record types.

Backing DNS Queries

Below are all DNS queries we submitted while inspecting the resource records.

DNSSEC

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.

Useful DNSSEC Tools

• Test dramaticwebsites.com @ DNSViz
• Test dramaticwebsites.com @ DNSSEC Analyzer (Verisign Labs)
• Zonemaster (iiS and AFNIC)

Certification Authority Authorization

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.

Email (SMTP)

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.

220 mx.zohocloud.ca SMTP Server ready April 26, 2025 7:38:37 PM EDT
EHLO outbound.hardenize.com
250-mx.zohocloud.ca Hello outbound.hardenize.com (outbound.hardenize.com (172.99.67.55))
250-STARTTLS
250-8BITMIME
250 SIZE 53477376
QUIT
221 mx.zohocloud.ca closing connection

220 mx.zohocloud.ca SMTP Server ready April 26, 2025 7:38:36 PM EDT
EHLO outbound.hardenize.com
250-mx.zohocloud.ca Hello outbound.hardenize.com (outbound.hardenize.com (172.99.67.55))
250-STARTTLS
250-8BITMIME
250 SIZE 53477376
QUIT
221 mx.zohocloud.ca closing connection

220 mx.zohocloud.ca SMTP Server ready April 26, 2025 7:38:37 PM EDT
EHLO outbound.hardenize.com
250-mx.zohocloud.ca Hello outbound.hardenize.com (outbound.hardenize.com (172.99.67.55))
250-STARTTLS
250-8BITMIME
250 SIZE 53477376
QUIT
221 mx.zohocloud.ca closing connection

Email TLS (SMTP)

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.

Email Certificates (SMTP)

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.

Certificate #1

Leaf certificate *.zohocloud.ca
Issuer: DigiCert
Not Before: 24 Jun 2024 00:00:00 UTC
Not After: 23 Jun 2025 23:59:59 UTC (expires in 1 month 28 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Names	*.zohocloud.ca zohocloud.ca zohoone.ca *.zohoone.ca
Subject DN	CN=*.zohocloud.ca
Subject Key Identifier	bcb678dc284dad0a390fbe48ef09ba99b4cd367f
Serial	3017fdb7303e3babe588df3f9f64d4f
Not Before	24 Jun 2024 00:00:00 UTC
Not After	23 Jun 2025 23:59:59 UTC
Validity period	365 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	24 Jun 2024 14:46:03 UTC | Google 'Argon2025h1' log | Qualified 24 Jun 2024 14:46:03 UTC | DigiCert Nessie2025 Log | Qualified 24 Jun 2024 14:46:03 UTC | Let's Encrypt 'Oak2025h1' | Qualified
Fingerprints
SHA1	b17f19f264404ed5c63d8ab6b7e0b1c03c3c667e
SHA256	6526f0425fe9f34722aed1d33a79d8040cc9a35fedfe4d286f2a584233d019c5
SPKI SHA256	1cf45aecdd504b76c7b48e61c8de0f6f1cba0fa48454f128114f8b124f2b019e

Analysis

Good

Strong private key

Good. The private key associated with this certificate is secure.

Good

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Good

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Good

Certificate dates match

Good. The certificate is valid for use at this point of time.

Good

Certificate has not been revoked

Good. This certificate has not been revoked.

Good

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate

*.zohocloud.ca | 6526f04
Not After: 23 Jun 2025 23:59:59 UTC (expires in 1 month 28 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Names	*.zohocloud.ca zohocloud.ca zohoone.ca *.zohoone.ca
Subject DN	CN=*.zohocloud.ca
Subject Key Identifier	bcb678dc284dad0a390fbe48ef09ba99b4cd367f
Serial	3017fdb7303e3babe588df3f9f64d4f
Not Before	24 Jun 2024 00:00:00 UTC
Not After	23 Jun 2025 23:59:59 UTC
Validity period	365 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	24 Jun 2024 14:46:03 UTC | Google 'Argon2025h1' log | Qualified 24 Jun 2024 14:46:03 UTC | DigiCert Nessie2025 Log | Qualified 24 Jun 2024 14:46:03 UTC | Let's Encrypt 'Oak2025h1' | Qualified
Fingerprints
SHA1	b17f19f264404ed5c63d8ab6b7e0b1c03c3c667e
SHA256	6526f0425fe9f34722aed1d33a79d8040cc9a35fedfe4d286f2a584233d019c5
SPKI SHA256	1cf45aecdd504b76c7b48e61c8de0f6f1cba0fa48454f128114f8b124f2b019e

Intermediate certificate

Thawte TLS RSA CA G1 | 4bcc5e2
Not After: 02 Nov 2027 12:24:25 UTC (expires in 2 years 6 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Subject DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Serial	90ee8c5de5bfa62d2ae2ff7097c4857
Not Before	02 Nov 2017 12:24:25 UTC
Not After	02 Nov 2027 12:24:25 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Not Applicable
Authority Key Identifier	keyid:4e2254201895e6e36ee60ffafab912ed06178f39
CRL	http://crl3.digicert.com/DigiCertGlobalRootG2.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	c9fefc763d9548b487696f047acba0abe45c7bc1
SHA256	4bcc5e234fe81ede4eaf883aa19c31335b0b26e85e066b9945e4cb6153eb20c2
SPKI SHA256	e366fd44d3a7c9bded942d0a62d34f03728aa4996eb24c94e9a1be0a2a5499a3

Root certificate

DigiCert Global Root G2 | cb3ccbb
Not After: 15 Jan 2038 12:00:00 UTC (expires in 12 years 8 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Subject DN	CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	4e2254201895e6e36ee60ffafab912ed06178f39
Serial	33af1e6a711a9a0bb2864b11d09fae5
Not Before	01 Aug 2013 12:00:00 UTC
Not After	15 Jan 2038 12:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	df3c24f9bfd666761b268073fe06d1cc8d4f82a4
SHA256	cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
SPKI SHA256	8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26

Email DANE (SMTP)

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.

SPF

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.

DMARC

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.

MTA Strict Transport Security

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

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.

HTTP (80)

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.

URL: http://dramaticwebsites.com/

HTTP (443)

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.

URL: https://dramaticwebsites.com/

WWW TLS

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.

WWW Certificates

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.

DANE (443)

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

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.

HTML Content

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.

HTTP Strict Transport Security

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.

HTTP Public Key Pinning

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

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.

Subresource Integrity

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

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.

Frame Options

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.

XSS Protection

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.

Content Type Options

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.