| 1. General Results, most used to calculate the result |
A | name "fadeev.org" is domain, public suffix is "org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
|
A | Good: All ip addresses are public addresses
|
A | Good: No asked Authoritative Name Server had a timeout
|
A | Good: destination is https
|
A | Good - only one version with Http-Status 200
|
A | Good: one preferred version: non-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://fadeev.org/ 104.198.14.52
| https://fadeev.org/
| Correct redirect http - https with the same domain name
|
A | http://www.fadeev.org/ 68.183.215.91
| https://www.fadeev.org/
| Correct redirect http - https with the same domain name
|
A | http://www.fadeev.org/ 2a03:b0c0:3:e0::298:6001
| https://www.fadeev.org/
| Correct redirect http - https with the same domain name
|
R | http://fadeev.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.198.14.52
| https://fadeev.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Redirect to not existing domain
|
R | http://www.fadeev.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 68.183.215.91
| https://www.fadeev.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Redirect to not existing domain
|
R | http://www.fadeev.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:b0c0:3:e0::298:6001
| https://www.fadeev.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Redirect to not existing domain
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 3. DNS- and NameServer - Checks |
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: ns1.digitalocean.com,ns1.hover.com,ns2.digitalocean.com,ns2.hover.com,ns3.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: ns1.digitalocean.com,ns1.hover.com,ns2.digitalocean.com,ns2.hover.com,ns3.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.hover.com (216.40.47.26): Delegation: ns1.digitalocean.com,ns1.hover.com,ns2.digitalocean.com,ns2.hover.com,ns3.digitalocean.com, Zone: ns1.hover.com,ns2.hover.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: ns1.digitalocean.com,ns1.hover.com,ns2.digitalocean.com,ns2.hover.com,ns3.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: ns1.digitalocean.com,ns1.hover.com,ns2.digitalocean.com,ns2.hover.com,ns3.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.hover.com (64.98.148.13): Delegation: ns1.digitalocean.com,ns1.hover.com,ns2.digitalocean.com,ns2.hover.com,ns3.digitalocean.com, Zone: ns1.hover.com,ns2.hover.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: ns1.digitalocean.com,ns1.hover.com,ns2.digitalocean.com,ns2.hover.com,ns3.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: ns1.digitalocean.com,ns1.hover.com,ns2.digitalocean.com,ns2.hover.com,ns3.digitalocean.com, Zone: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com
|
A | Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
|
A | Good: Nameserver supports TCP connections: 8 good Nameserver
|
A | Good: Nameserver supports Echo Capitalization: 8 good Nameserver
|
X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.hover.com
|
X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.hover.com
|
A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hover.com / 216.40.47.26: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: ok (hover02.dns.bra.prod.tucows.net). COOKIE: ok. CLIENTSUBNET: no result.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.hover.com / 64.98.148.13: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: ok (hover01.dns.ash.prod.tucows.net). COOKIE: ok. 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://fadeev.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Fatal: Check of /.well-known/acme-challenge/random-filename redirects to not-existing domain. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://www.fadeev.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Fatal: Check of /.well-known/acme-challenge/random-filename redirects to not-existing domain. Creating a Letsencrypt certificate via http-01 challenge can't work. 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://fadeev.org/ 104.198.14.52
|
| 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://fadeev.org/ 104.198.14.52
|
| 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.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 1 external CSS / JavaScript files without GZip found - 5 with GZip, 6 complete
|
A | Good: All images with internal compression not compressed. Some Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so an additional compression isn't helpful. 2 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed
|
| 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, 5 with Cache-Control max-age too short (minimum 7 days), 1 with Cache-Control long enough, 6 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 3 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 3 complete.
|
A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
A | Good: All img-elements have a valid alt-attribute.: 3 img-elements found.
|
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
|
A | Duration: 138267 milliseconds, 138.267 seconds
|