| 1. General Results, most used to calculate the result |
A | name "thetacticalbrief.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
|
A | Good: All ip addresses are public addresses
|
A | Good: No asked Authoritative Name Server had a timeout
|
A | DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
|
A | Good: destination is https
|
A | Good - only one version with Http-Status 200
|
A | Good: one preferred version: www is preferred
|
A | Good: every https has a Strict Transport Security Header
|
A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
|
A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
A | http://thetacticalbrief.com/ 134.209.226.211
| https://thetacticalbrief.com/
| Correct redirect http - https with the same domain name
|
A | http://www.thetacticalbrief.com/ 167.99.137.12
| https://www.thetacticalbrief.com/
| Correct redirect http - https with the same domain name
|
M | https://134.209.226.211/ 134.209.226.211
|
| Misconfiguration - main pages should never send http status 400 - 499
|
M | https://167.99.137.12/ 167.99.137.12
|
| Misconfiguration - main pages should never send http status 400 - 499
|
N | https://134.209.226.211/ 134.209.226.211
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
N | https://167.99.137.12/ 167.99.137.12
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 3. DNS- and NameServer - Checks |
A | Info:: 18 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 9 Name Servers.
|
A | Info:: 18 Queries complete, 14 with IPv6, 4 with IPv4.
|
| Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
|
A | Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.dns1.p01.nsone.net (198.51.44.1), dns1.p01.nsone.net (198.51.44.1), dns2.p01.nsone.net (198.51.45.1), dns3.p01.nsone.net (198.51.44.65), dns4.p01.nsone.net (198.51.45.65)
|
A | Good (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers.
|
A | Info:: 9 different Name Servers found: dns1.p01.nsone.net, dns1.p04.nsone.net, dns2.p01.nsone.net, dns2.p04.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 4 Name Servers included in Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, 7 Name Servers included in 2 Zone definitions: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 2 Name Servers listed in SOA.Primary: dns1.p01.nsone.net, ns1.digitalocean.com.
|
| Error: Different SOA.Primary Name Servers found, different SOA Definitions.: dns1.p01.nsone.net,ns1.digitalocean.com.
|
| Error: SOA.Primary Name Server not included in the delegation set.: dns1.p01.nsone.net,ns1.digitalocean.com.
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.digitalocean.com (173.245.59.41): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.digitalocean.com (2400:cb00:2049:1::adf5:3b29): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.digitalocean.com (198.41.222.173): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.digitalocean.com (2400:cb00:2049:1::c629:dead): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns1.p01.nsone.net (198.51.44.1): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns1.p04.nsone.net (198.51.44.4): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns2.p01.nsone.net (198.51.45.1): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns2.p04.nsone.net (198.51.45.4): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns3.p01.nsone.net (198.51.44.65): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns4.p01.nsone.net (198.51.45.65): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.digitalocean.com (173.245.58.51): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.digitalocean.com (2400:cb00:2049:1::adf5:3a33): Delegation: dns1.p04.nsone.net, dns2.p04.nsone.net, ns1.digitalocean.com, ns2.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
|
A | Good: All Name Server Domain Names have a Public Suffix.
|
A | Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
|
A | Good: All Name Server ip addresses are public.
|
A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 9 different Name Servers found
|
A | Good: Some Name Servers have IPv6 addresses: 3 Name Servers with IPv6 found (6 Name Servers without IPv6)
|
A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 9 Name Servers, 2 Top Level Domains: net, com
|
A | Good: Name Servers with different domain names found.: 2 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 9 Name Servers, 1 Countries: US
|
A | Info: Ipv4-Subnet-list: 9 Name Servers, 2 different subnets (first Byte): 173., 198., 3 different subnets (first two Bytes): 173.245., 198.41., 198.51., 5 different subnets (first three Bytes): 173.245.58., 173.245.59., 198.41.222., 198.51.44., 198.51.45.
|
A | Good: Name Server IPv4-addresses from different subnet found:
|
A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2400:, 1 different subnets (first two blocks): 2400:cb00:, 1 different subnets (first three blocks): 2400:cb00:2049:, 1 different subnets (first four blocks): 2400:cb00:2049:0001:
|
| Fatal: All Name Server IPv6 addresses from the same subnet.
|
A | Good: Nameserver supports TCP connections: 12 good Nameserver
|
A | Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
|
A | Good: Nameserver supports Echo Capitalization: 12 good Nameserver
|
A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
|
A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.digitalocean.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
|
X | Fatal error: Nameservers with different SOA Serial Numbers
|
| Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
|
| 4. Content- and Performance-critical Checks |
| https://www.thetacticalbrief.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://www.thetacticalbrief.com/ 167.99.137.12
|
| Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
|
| https://www.thetacticalbrief.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
|
| https://www.thetacticalbrief.com/ 167.99.137.12
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
| https://www.thetacticalbrief.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| https://www.thetacticalbrief.com/ 167.99.137.12
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async.
|
| https://www.thetacticalbrief.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 2 external CSS / JavaScript files without GZip found - 6 with GZip, 8 complete
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 8 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 8 complete.
|
A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
A | Info: No img element found, no alt attribute checked
|
A | Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
|
| https://134.209.226.211/ 134.209.226.211
| 2.333 seconds
| Warning: 404 needs more then one second
|
| https://167.99.137.12/ 167.99.137.12
| 2.330 seconds
| Warning: 404 needs more then one second
|
A | Duration: 175990 milliseconds, 175.990 seconds
|