| 1. General Results, most used to calculate the result |
| A | name "turnosweb.jussanjuan.gob.ar" is subdomain, public suffix is "gob.ar", top-level-domain-type is "country-code", Country is Argentina, tld-manager is "Presidencia de la Nación – Secretaría Legal y Técnica"
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: turnosweb.jussanjuan.gob.ar 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: turnosweb.jussanjuan.gob.ar has no ipv6 address.
|
| 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: one preferred version: non-www is preferred
|
| 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 (4 urls)
|
| http://turnosweb.jussanjuan.gob.ar/ 200.41.226.185
|
| Url with incomplete Content-Type - header - missing charset
|
| https://turnosweb.jussanjuan.gob.ar/ 200.41.226.185
|
| Url with incomplete Content-Type - header - missing charset
|
| http://turnosweb.jussanjuan.gob.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.41.226.185
|
| Url with incomplete Content-Type - header - missing charset
|
| https://200.41.226.185/ 200.41.226.185
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://turnosweb.jussanjuan.gob.ar/ 200.41.226.185
|
| Missing HSTS-Header
|
| B | https://200.41.226.185/ 200.41.226.185
|
| Missing HSTS-Header
|
| 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.
|
| N | https://turnosweb.jussanjuan.gob.ar/ 200.41.226.185
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://200.41.226.185/ 200.41.226.185
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.huaweicloud-dns.net / 159.138.112.21
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.huaweicloud-dns.net / 159.138.76.159
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.huaweicloud-dns.org / 159.138.17.59
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.huaweicloud-dns.org / 159.138.77.159
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.com / 122.112.208.53
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.com / 139.159.208.43
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.com / 139.159.208.46
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.com / 139.9.224.17
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.com / 159.138.16.55
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.com / 159.138.17.59
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.com / 159.138.76.159
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.com / 159.138.77.159
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.net / 122.112.208.53
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.net / 159.138.16.55
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.net / 159.138.17.59
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.net / 159.138.76.159
|
| X | Fatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.hwclouds-dns.net / 159.138.77.159
|
| 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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain turnosweb.jussanjuan.gob.ar, 1 ip addresses, 1 different http results.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Info:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 9 Queries complete, 8 with IPv6, 0 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.ns1.hwclouds-dns.com (122.112.208.53, 139.159.208.43, 139.159.208.46, 139.9.224.17, 159.138.16.55, 159.138.17.59, 159.138.76.159, 159.138.77.159, 2407:c080:0:ffff:ffff:fffe:0:1), ns1.hwclouds-dns.net (139.159.208.43, 139.159.208.46, 159.138.16.55, 159.138.17.59, 159.138.76.159, 159.138.77.159, 2407:c080:0:ffff:ffff:fffe:0:1, 49.4.112.16)
|
| A | Good (1 - 3.0):: An average of 2.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 5 different Name Servers found: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.com, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, 4 Name Servers included in Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, 2 Name Servers included in 2 Zone definitions: ns1.hwclouds-dns.com, ns1.hwclouds-dns.net, 1 Name Servers listed in SOA.Primary: ns1.hwclouds-dns.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.hwclouds-dns.com.
|
| Error: SOA.Primary Name Server not included in the delegation set.: ns1.hwclouds-dns.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.hwclouds-dns.net (122.112.208.53): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.net (139.159.208.43): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.net (139.159.208.46): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.net (159.138.16.55): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.net (159.138.17.59): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.net (159.138.76.159): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.net (159.138.77.159): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.net (49.4.112.16): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.net (2407:c080:0:ffff:ffff:fffe:0:1): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.huaweicloud-dns.net (159.138.112.21): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.huaweicloud-dns.net (159.138.76.159): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.huaweicloud-dns.org (159.138.17.59): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.huaweicloud-dns.org (159.138.77.159): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.com (122.112.208.53): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.com (139.159.208.43): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.com (139.159.208.46): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.com (139.9.224.17): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.com (159.138.16.55): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.com (159.138.17.59): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.com (159.138.76.159): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.com (159.138.77.159): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.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.hwclouds-dns.com (2407:c080:0:ffff:ffff:fffe:0:1): Delegation: ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, ns1.hwclouds-dns.net, ns1.hwclouds-dns.org, Zone: ns1.hwclouds-dns.com, ns1.hwclouds-dns.net
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1
|
|
|
| A | Info: Ipv4-Subnet-list: 20 Name Servers, 4 different subnets (first Byte): 122., 139., 159., 49., 5 different subnets (first two Bytes): 122.112., 139.159., 139.9., 159.138., 49.4., 9 different subnets (first three Bytes): 122.112.208., 139.159.208., 139.9.224., 159.138.112., 159.138.16., 159.138.17., 159.138.76., 159.138.77., 49.4.112.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2407:, 1 different subnets (first two blocks): 2407:c080:, 1 different subnets (first three blocks): 2407:c080:0000:, 1 different subnets (first four blocks): 2407:c080:0000:ffff:
|
| Fatal: All Name Server IPv6 addresses from the same subnet.
|
| A | Good: Nameserver supports TCP connections: 22 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: ns1.hwclouds-dns.com / 2407:c080:0:ffff:ffff:fffe:0:1
|
| X | Nameserver Timeout checking Echo Capitalization: ns1.hwclouds-dns.net / 139.159.208.43
|
| X | Nameserver Timeout checking Echo Capitalization: ns1.hwclouds-dns.net / 139.159.208.46
|
| X | Nameserver Timeout checking Echo Capitalization: ns1.hwclouds-dns.net / 49.4.112.16
|
| X | Nameserver Timeout checking Echo Capitalization: ns1.hwclouds-dns.net / 2407:c080:0:ffff:ffff:fffe:0:1
|
| X | Nameserver Timeout checking EDNS512: ns1.hwclouds-dns.com / 122.112.208.53
|
| X | Nameserver Timeout checking EDNS512: ns1.hwclouds-dns.com / 139.159.208.46
|
| X | Nameserver Timeout checking EDNS512: ns1.hwclouds-dns.net / 139.159.208.43
|
| X | Nameserver Timeout checking EDNS512: ns1.hwclouds-dns.net / 49.4.112.16
|
| X | Nameserver Timeout checking EDNS512: ns1.hwclouds-dns.net / 2407:c080:0:ffff:ffff:fffe:0:1
|
| Nameserver doesn't pass all EDNS-Checks: ns1.huaweicloud-dns.net / 159.138.76.159: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.huaweicloud-dns.net / 159.138.112.21: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.huaweicloud-dns.org / 159.138.17.59: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.huaweicloud-dns.org / 159.138.77.159: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.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.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.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.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.com / 122.112.208.53: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: fatal timeout. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.com / 139.9.224.17: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: fatal timeout. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.com / 139.159.208.43: OP100: fatal timeout. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: fatal timeout. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.com / 139.159.208.46: OP100: ok. FLAGS: fatal timeout. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.com / 159.138.16.55: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.com / 159.138.17.59: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.com / 159.138.76.159: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.com / 159.138.77.159: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.com / 2407:c080:0:ffff:ffff:fffe:0:1: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.net / 49.4.112.16: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.net / 122.112.208.53: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.net / 139.159.208.43: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: fatal timeout. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.net / 139.159.208.46: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.net / 159.138.16.55: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.net / 159.138.17.59: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.net / 159.138.76.159: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.net / 159.138.77.159: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.net / 2407:c080:0:ffff:ffff:fffe:0:1: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hwclouds-dns.org: 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.
|
| 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://turnosweb.jussanjuan.gob.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.41.226.185
|
| 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://turnosweb.jussanjuan.gob.ar/ 200.41.226.185
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://200.41.226.185/ 200.41.226.185
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://turnosweb.jussanjuan.gob.ar/ 200.41.226.185
|
| 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://200.41.226.185/ 200.41.226.185
|
| 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 %.
|
| https://turnosweb.jussanjuan.gob.ar/ 200.41.226.185
|
| 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://200.41.226.185/ 200.41.226.185
|
| 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://turnosweb.jussanjuan.gob.ar/ 200.41.226.185
|
| 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.: 6 script elements without defer/async.
|
| http://turnosweb.jussanjuan.gob.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.41.226.185
|
| 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.: 6 script elements without defer/async.
|
| https://200.41.226.185/ 200.41.226.185
|
| 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.: 6 script elements without defer/async.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 21 external CSS / JavaScript files without GZip found - 6 with GZip, 27 complete
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 21 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 6 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 27 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
|
| A | Duration: 688847 milliseconds, 688.847 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)