| 1. General Results, most used to calculate the result |
| A | name "hazmi.id" is domain, public suffix is ".id", top-level-domain is ".id", top-level-domain-type is "country-code", Country is Indonesia, tld-manager is "Perkumpulan Pengelola Nama Domain Internet Indonesia (PANDI)", num domains preloaded: 189
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: hazmi.id has only one ip address.
|
| Warning: Only one ip address found: www.hazmi.id has only one ip 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: hazmi.id 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.hazmi.id has no ipv6 address.
|
| 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://hazmi.id/ 104.198.14.52
| https://hazmi.id/
| Correct redirect http - https with the same domain name
|
| A | http://www.hazmi.id/ 104.198.14.52
| https://www.hazmi.id/
| Correct redirect http - https with the same domain name
|
| M | https://104.198.14.52/ 104.198.14.52
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://104.198.14.52/ 104.198.14.52
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain hazmi.id, 1 ip addresses.
|
| Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain www.hazmi.id, 1 ip addresses.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Info:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: ns-1073.awsdns-06.org, ns-1777.awsdns-30.co.uk, ns-313.awsdns-39.com, ns-929.awsdns-52.net, 4 Name Servers included in Delegation: ns-1073.awsdns-06.org, ns-1777.awsdns-30.co.uk, ns-313.awsdns-39.com, ns-929.awsdns-52.net, 4 Name Servers included in 1 Zone definitions: ns-1073.awsdns-06.org, ns-1777.awsdns-30.co.uk, ns-313.awsdns-39.com, ns-929.awsdns-52.net, 1 Name Servers listed in SOA.Primary: ns-313.awsdns-39.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns-313.awsdns-39.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns-313.awsdns-39.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: ns-1073.awsdns-06.org, ns-1777.awsdns-30.co.uk, ns-313.awsdns-39.com, ns-929.awsdns-52.net
|
| 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: 4 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 4 Top Level Domains: org, net, com, co.uk
|
| A | Good: Name Servers with different domain names found.: 4 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.193., 205.251.195., 205.251.196., 205.251.198.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5301:, 2600:9000:5303:, 2600:9000:5304:, 2600:9000:5306:, 4 different subnets (first four blocks): 2600:9000:5301:3900:, 2600:9000:5303:a100:, 2600:9000:5304:3100:, 2600:9000:5306:f100:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 8 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 8 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns4.apnic.net: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns4-de1.apnic.net). 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 |
| https://hazmi.id/.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://hazmi.id/ 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://hazmi.id/.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.
|
| A | Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| A | Good: All script Elements (type text/javascript) and src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 2 external CSS / JavaScript files without GZip found - 12 with GZip, 14 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, 14 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 14 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, 4 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 4 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 4 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
|
| https://104.198.14.52/ 104.198.14.52
| 3.990 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 138747 milliseconds, 138.747 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)