| 1. General Results, most used to calculate the result |
| A | name "nazi.us" is domain, public suffix is ".us", top-level-domain is ".us", top-level-domain-type is "country-code", Country is United States of America (the), tld-manager is "NeuStar, Inc.", num .us-domains preloaded: 746 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: nazi.us has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.nazi.us has 2 different ip addresses (authoritative).
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: nazi.us has no ipv6 address.
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.nazi.us has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: No cookie sent via http.
|
| 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (12 urls)
|
| http://nazi.us/ 13.248.169.48
|
| Url with incomplete Content-Type - header - missing charset
|
| http://nazi.us/ 76.223.54.146
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.nazi.us/ 13.248.169.48
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.nazi.us/ 76.223.54.146
|
| Url with incomplete Content-Type - header - missing charset
|
| https://nazi.us/ 13.248.169.48
|
| Url with incomplete Content-Type - header - missing charset
|
| https://nazi.us/ 76.223.54.146
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.nazi.us/ 13.248.169.48
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.nazi.us/ 76.223.54.146
|
| Url with incomplete Content-Type - header - missing charset
|
| http://nazi.us/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.169.48
|
| Url with incomplete Content-Type - header - missing charset
|
| http://nazi.us/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.54.146
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.nazi.us/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.169.48
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.nazi.us/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.54.146
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://nazi.us/ 13.248.169.48
|
| Missing HSTS-Header
|
| B | https://nazi.us/ 76.223.54.146
|
| Missing HSTS-Header
|
| B | https://www.nazi.us/ 13.248.169.48
|
| Missing HSTS-Header
|
| B | https://www.nazi.us/ 76.223.54.146
|
| Missing HSTS-Header
|
| C | Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
|
| C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
| H | Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain nazi.us, 2 ip addresses.
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.nazi.us, 2 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain nazi.us, 2 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.nazi.us, 2 ip addresses.
|
| A | Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.nazi.us
|
| B | Bad: _mta-sts TXT found, but invalid
|
| 2. Header-Checks |
| F | nazi.us 13.248.169.48
| Content-Security-Policy
| Critical: Missing Header:
|
| F | nazi.us 13.248.169.48
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | nazi.us 13.248.169.48
| Referrer-Policy
| Critical: Missing Header:
|
| F | nazi.us 13.248.169.48
| Permissions-Policy
| Critical: Missing Header:
|
| B | nazi.us 13.248.169.48
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | nazi.us 13.248.169.48
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | nazi.us 13.248.169.48
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | nazi.us 76.223.54.146
| Content-Security-Policy
| Critical: Missing Header:
|
| F | nazi.us 76.223.54.146
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | nazi.us 76.223.54.146
| Referrer-Policy
| Critical: Missing Header:
|
| F | nazi.us 76.223.54.146
| Permissions-Policy
| Critical: Missing Header:
|
| B | nazi.us 76.223.54.146
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | nazi.us 76.223.54.146
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | nazi.us 76.223.54.146
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.nazi.us 13.248.169.48
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.nazi.us 13.248.169.48
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.nazi.us 13.248.169.48
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.nazi.us 13.248.169.48
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.nazi.us 13.248.169.48
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.nazi.us 13.248.169.48
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.nazi.us 13.248.169.48
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.nazi.us 76.223.54.146
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.nazi.us 76.223.54.146
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.nazi.us 76.223.54.146
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.nazi.us 76.223.54.146
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.nazi.us 76.223.54.146
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.nazi.us 76.223.54.146
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.nazi.us 76.223.54.146
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 9 Queries complete, 9 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 4.5 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.afternic.com, ns2.afternic.com, 2 Name Servers included in Delegation: ns1.afternic.com, ns2.afternic.com, 2 Name Servers included in 1 Zone definitions: ns1.afternic.com, ns2.afternic.com, 2 Name Servers listed in SOA.Primary: ns1.afternic.com, ns2.afternic.com.
|
| Error: Different SOA.Primary Name Servers found, different SOA Definitions.: ns1.afternic.com,ns2.afternic.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.afternic.com,ns2.afternic.com.
|
| A | Good: Consistency 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. Ordered list of name servers: ns1.afternic.com, ns2.afternic.com
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
|
| Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
|
| Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: afternic.com
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
|
| A |
|
| A | Good: Nameserver supports TCP connections: 4 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: a.cctld.us: 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.
|
| Nameserver doesn't pass all EDNS-Checks: y.cctld.us: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: ok (dns2.defra1). COOKIE: ok. CLIENTSUBNET: ok.
|
| A | Good: All SOA have the same Serial Number
|
| 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 |
| http://nazi.us/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.169.48
|
| 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.
|
| http://nazi.us/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.54.146
|
| 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.
|
| http://www.nazi.us/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.169.48
|
| 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.
|
| http://www.nazi.us/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.54.146
|
| 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.
|
| https://nazi.us/ 13.248.169.48
|
| 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://nazi.us/ 76.223.54.146
|
| 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.nazi.us/ 13.248.169.48
|
| 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.nazi.us/ 76.223.54.146
|
| 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://nazi.us/ 13.248.169.48
|
| 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://nazi.us/ 76.223.54.146
|
| 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.nazi.us/ 13.248.169.48
|
| 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.nazi.us/ 76.223.54.146
|
| 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://nazi.us/ 13.248.169.48
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| https://nazi.us/ 76.223.54.146
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| https://www.nazi.us/ 13.248.169.48
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| https://www.nazi.us/ 76.223.54.146
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| 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
|
| A | Duration: 730607 milliseconds, 730.607 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)