Check DNS, Urls + Redirects, Certificates and Content of your Website



P

Tls-Protocol error

Checked:
29.03.2021 16:08:44


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
tedhardy.com
A
167.71.81.39
Clifton/New Jersey/United States (US) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA
2604:a880:800:c1::3a1:4001
Clifton/New Jersey/United States (US) - DigitalOcean, LLC

yes


www.tedhardy.com
A
167.71.81.39
Clifton/New Jersey/United States (US) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA

yes


*.tedhardy.com
A
167.71.81.39
yes



AAAA

yes



CNAME

yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 14631, Flags 256



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 42351, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 12.04.2021, 00:00:00 +, Signature-Inception: 22.03.2021, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 11.04.2021, 05:00:00 +, Signature-Inception: 29.03.2021, 04:00:00 +, KeyTag 42351, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 42351 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 58540, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.04.2021, 18:24:21 +, Signature-Inception: 21.03.2021, 18:19:21 +, KeyTag 30909, Signer-Name: com



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: tedhardy.com
tedhardy.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "cavsipes1ja380t0nnmdkj3jfs4b8kgq" between the hashed NSEC3-owner "cavs8puc6rd50uvhenhgj29q8b3veccj" and the hashed NextOwner "cavta0lmo8v291qflvebo190eu9krn94". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner cavs8puc6rd50uvhenhgj29q8b3veccj.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 05.04.2021, 13:47:21 +, Signature-Inception: 29.03.2021, 12:37:21 +, KeyTag 58540, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "tedhardy.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.04.2021, 04:24:10 +, Signature-Inception: 26.03.2021, 03:14:10 +, KeyTag 58540, Signer-Name: com



0 DNSKEY RR found




Zone: www.tedhardy.com
www.tedhardy.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
tedhardy.com
  ns1.hover.com / hover03.dns.bra.prod.tucows.net
216.40.47.26
Mississauga/Ontario/Canada (CA) - Tucows.com Co.


  ns2.hover.com / hover06.dns.ash.prod.tucows.net
64.98.148.13
Old Toronto/Ontario/Canada (CA) - Tucows.com Co.

com
  a.gtld-servers.net / nnn1-was1


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-was1


  d.gtld-servers.net / nnn1-was1


  e.gtld-servers.net / nnn1-was1


  f.gtld-servers.net / nnn1-ams6


  g.gtld-servers.net / nnn1-ams6


  h.gtld-servers.net / nnn1-ams6


  i.gtld-servers.net / nnn1-ams6


  j.gtld-servers.net / nnn1-lon5


  k.gtld-servers.net / nnn1-lon5


  l.gtld-servers.net / nnn1-lon5


  m.gtld-servers.net / nnn1-lon5


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1617026907
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:9


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1617026922
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:tedhardy.com
Zone-Name:tedhardy.com
Primary:ns1.hover.com
Mail:dnsmaster.hover.com
Serial:1502458598
Refresh:10800
Retry:3600
Expire:604800
TTL:900
num Entries:2


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://tedhardy.com/
167.71.81.39
301
https://tedhardy.com/
Html is minified: 109.46 %
0.197
A
Server: nginx
Date: Mon, 29 Mar 2021 14:09:43 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Location: https://tedhardy.com/

• http://www.tedhardy.com/
167.71.81.39
301
https://highgravityconsulting.com/
Html is minified: 109.46 %
0.203
E
Server: nginx
Date: Mon, 29 Mar 2021 14:09:53 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Location: https://highgravityconsulting.com/

• http://tedhardy.com/
2604:a880:800:c1::3a1:4001
-14

10.024
T
Timeout - The operation has timed out

• https://tedhardy.com/
167.71.81.39
-10

0.190
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• https://tedhardy.com/
2604:a880:800:c1::3a1:4001
-14

10.037
T
Timeout - The operation has timed out

• https://www.tedhardy.com/
167.71.81.39
-10

0.197
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• https://highgravityconsulting.com/

-14

10.000
T
Timeout - The operation has timed out

• http://tedhardy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
167.71.81.39
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.61 %
0.193
A
Not Found
Visible Content: 404 Not Found nginx
Server: nginx
Date: Mon, 29 Mar 2021 14:10:08 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 146
Connection: close

• http://tedhardy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2604:a880:800:c1::3a1:4001
-14

10.064
T
Timeout - The operation has timed out
Visible Content:

• http://www.tedhardy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
167.71.81.39
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.61 %
0.617
A
Not Found
Visible Content: 404 Not Found nginx
Server: nginx
Date: Mon, 29 Mar 2021 14:10:19 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 146
Connection: close

• https://167.71.81.39/
167.71.81.39
-10

0.193
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• https://[2604:a880:0800:00c1:0000:0000:03a1:4001]/
2604:a880:800:c1::3a1:4001
-14

10.030
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "tedhardy.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 57967 (complete: 151507)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: tedhardy.com has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: tedhardy.com has 1 ipv4, 1 ipv6 addresses
Warning: Only one ip address found: www.tedhardy.com 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: www.tedhardy.com has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: 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.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - no version with Http-Status 200
Ehttp://www.tedhardy.com/ 167.71.81.39
301
https://highgravityconsulting.com/
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
HFatal error: No https - result with http-status 200, no encryption
Khttp://tedhardy.com/ 167.71.81.39, Status 301

http://tedhardy.com/ 2604:a880:800:c1::3a1:4001, Status -14
Configuration problem - different ip addresses with different status
Khttps://tedhardy.com/ 167.71.81.39, Status -10

https://tedhardy.com/ 2604:a880:800:c1::3a1:4001, Status -14
Configuration problem - different ip addresses with different status
Khttp://tedhardy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.71.81.39, Status 404

http://tedhardy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:800:c1::3a1:4001, Status -14
Configuration problem - different ip addresses with different status
Phttps://tedhardy.com/ 167.71.81.39
-10

Error creating a TLS-Connection: TLSv1.3 found, but no connection via TLSv1.2 possible. Please activate TLSv1.2
Phttps://www.tedhardy.com/ 167.71.81.39
-10

Error creating a TLS-Connection: TLSv1.3 found, but no connection via TLSv1.2 possible. Please activate TLSv1.2
Phttps://167.71.81.39/ 167.71.81.39
-10

Error creating a TLS-Connection: TLSv1.3 found, but no connection via TLSv1.2 possible. Please activate TLSv1.2
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain tedhardy.com, 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 tedhardy.com, 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.tedhardy.com, 1 ip addresses.

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)


3. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: 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.hover.com (216.40.47.26), ns2.hover.com (64.98.148.13)
AGood (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.hover.com, ns2.hover.com, 2 Name Servers included in Delegation: ns1.hover.com, ns2.hover.com, 2 Name Servers included in 1 Zone definitions: ns1.hover.com, ns2.hover.com, 1 Name Servers listed in SOA.Primary: ns1.hover.com.
AGood: Only one SOA.Primary Name Server found.: ns1.hover.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.hover.com.
AGood: 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.hover.com, ns2.hover.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 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: hover.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: CA
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 216., 64., 2 different subnets (first two Bytes): 216.40., 64.98., 2 different subnets (first three Bytes): 216.40.47., 64.98.148.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.hover.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.hover.com
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 13 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 (hover03.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 (hover06.dns.ash.prod.tucows.net). COOKIE: ok. CLIENTSUBNET: no result.
AGood: 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://tedhardy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:800:c1::3a1:4001
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://tedhardy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:800:c1::3a1:4001, Status -14

http://tedhardy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.71.81.39, Status 404
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 140030 milliseconds, 140.030 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Small Code Update - wait one minute


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Small Code Update - wait one minute


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.hover.com, ns2.hover.com

QNr.DomainTypeNS used
1
com
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns1.hover.com: 216.40.47.26
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2.hover.com
64.98.148.13

Answer: ns3.hover.com
64.99.96.33


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.tedhardy.com
0

no CAA entry found
1
0
tedhardy.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tedhardy.com
google-site-verification=AH4LYDwPjfUT5seNZacYExMPKaxgY0aKQnAoOQPwU7M
ok
1
0
www.tedhardy.com

ok
1
0
_acme-challenge.tedhardy.com

missing entry or wrong length
1
0
_acme-challenge.www.tedhardy.com

missing entry or wrong length
1
0
_acme-challenge.tedhardy.com.tedhardy.com

perhaps wrong
1
0
_acme-challenge.www.tedhardy.com.tedhardy.com

perhaps wrong
1
0
_acme-challenge.www.tedhardy.com.www.tedhardy.com

perhaps wrong
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=51a9c12c-19c6-45a5-ac50-8cf1214dcec2


Last Result: https://check-your-website.server-daten.de/?q=tedhardy.com - 2021-03-29 16:08:44


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=tedhardy.com" target="_blank">Check this Site: tedhardy.com</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro