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



V

Connect failure - perhaps firewall

Checked:
23.10.2019 15:43:49


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
tlsseminar2019.space
A
162.255.119.38
Phoenix/Arizona/United States (US) - Namecheap
No Hostname found
yes
1
0

AAAA

yes


www.tlsseminar2019.space
CNAME
parkingpage.namecheap.com
yes
1
0

A
198.54.117.210
Newark/New Jersey/United States (US) - Namecheap, Inc.
Hostname: parkingpage.namecheap.com
yes



A
198.54.117.211
Newark/New Jersey/United States (US) - Namecheap, Inc.
Hostname: parkingpage.namecheap.com
yes



A
198.54.117.212
Newark/New Jersey/United States (US) - Namecheap, Inc.
Hostname: parkingpage.namecheap.com
yes



A
198.54.117.215
Newark/New Jersey/United States (US) - Namecheap, Inc.
No Hostname found
yes



A
198.54.117.216
Newark/New Jersey/United States (US) - Namecheap, Inc.
No Hostname found
yes



A
198.54.117.217
Newark/New Jersey/United States (US) - Namecheap, Inc.
No Hostname found
yes



A
198.54.117.218
Newark/New Jersey/United States (US) - Namecheap, Inc.
No Hostname found
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



Status: Valid because published



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.11.2019, 00:00:00 +, Signature-Inception: 21.10.2019, 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: space
space
2 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner space., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.11.2019, 05:00:00 +, Signature-Inception: 23.10.2019, 04:00:00 +, KeyTag 22545, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 25599, Flags 256



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



Public Key with Algorithm 8, KeyTag 47020, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner space., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 08.11.2019, 17:31:08 +, Signature-Inception: 09.10.2019, 17:52:22 +, KeyTag 44251, Signer-Name: space



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 44251, DigestType 1 and Digest "Nqy2i3NN/kZcwREvnawIuLZmJ8w=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



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

Zone: tlsseminar2019.space
tlsseminar2019.space
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 "untkgkv3h569mi2kdv2qaeipdl64aub8" between the hashed NSEC3-owner "ungr8divcj6lecn04jefgbsji69b666v" and the hashed NextOwner "uogs8ptr1hckhd2t1oclguu5n74l7p8e". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ungr8divcj6lecn04jefgbsji69b666v.space., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2019, 05:38:12 +, Signature-Inception: 09.10.2019, 17:52:22 +, KeyTag 25599, Signer-Name: space



0 DNSKEY RR found




Zone: www.tlsseminar2019.space
www.tlsseminar2019.space
0 DS RR in the parent zone found

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



Status: Valid because published



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.11.2019, 00:00:00 +, Signature-Inception: 21.10.2019, 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



1 RRSIG RR to validate DS RR found



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



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 12163, Flags 256



Public Key with Algorithm 8, KeyTag 17708, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 02.11.2019, 18:24:21 +, Signature-Inception: 18.10.2019, 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: namecheap.com
namecheap.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 "jf8ibbu63ilnulb42sf7in8rf44rm3q2" between the hashed NSEC3-owner "jf8hvi0vfemtvvj9tkblmu3ff4ffenlm" and the hashed NextOwner "jf8ipqg2bvhg0vjbgojk25nmh4fuaarn". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner jf8hvi0vfemtvvj9tkblmu3ff4ffenlm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 30.10.2019, 04:20:29 +, Signature-Inception: 23.10.2019, 03:10:29 +, KeyTag 12163, Signer-Name: com



0 DNSKEY RR found




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



0 DNSKEY RR found




3. Name Servers

DomainNameserverNS-IP
tlsseminar2019.space
  dns1.registrar-servers.com
216.87.155.33
Amsterdam/North Holland/Netherlands (NL) - VeriSign Global Registry Services


 
2620:74:19::33
Reston/Virginia/United States (US) - VeriSign Global Registry Services


  dns2.registrar-servers.com
216.87.152.33
Dallas/Texas/United States (US) - VeriSign Global Registry Services


 
2001:502:cbe4::33
Reston/Virginia/United States (US) - VeriSign Global Registry Services

space
  a.nic.space / NRDT-75SODK-AB8TIQ


  b.nic.space / FMCL-UEZCAO-YJSSPL


  c.nic.space / hivecast-23-cator.as15135.net Radix-C


  d.nic.space / hivecast-2-defra.as15135.net Radix-D


parkingpage.namecheap.com
  a1.verisigndns.com
209.112.113.33
Amsterdam/North Holland/Netherlands (NL) - VeriSign Global Registry Services


 
2001:500:7967::2:33
Reston/Virginia/United States (US) - VeriSign Global Registry Services

namecheap.com
  a1.verisigndns.com


  a2.verisigndns.com


  a3.verisigndns.com

com
  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


4. SOA-Entries


Domain:space
Zone-Name:
Primary:ns0.centralnic.net
Mail:hostmaster.centralnic.net
Serial:3000377181
Refresh:900
Retry:1800
Expire:6048000
TTL:3600
num Entries:4


Domain:tlsseminar2019.space
Zone-Name:
Primary:dns1.registrar-servers.com
Mail:hostmaster.registrar-servers.com
Serial:2019092601
Refresh:43200
Retry:3600
Expire:604800
TTL:3601
num Entries:4



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


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


Domain:namecheap.com
Zone-Name:
Primary:a1.verisigndns.com
Mail:hostmaster.cscdns.net
Serial:2008083479
Refresh:28800
Retry:7200
Expire:604800
TTL:3600
num Entries:3


Domain:parkingpage.namecheap.com
Zone-Name:
Primary:a1.verisigndns.com
Mail:hostmaster.cscdns.net
Serial:2008083479
Refresh:28800
Retry:7200
Expire:604800
TTL:3600
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://tlsseminar2019.space/
162.255.119.38
302
http://www.tlsseminar2019.space/?from=@
Html is minified: 103.33 %
0.370
D
Server: nginx
Date: Wed, 23 Oct 2019 13:44:36 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 62
Connection: close
Location: http://www.tlsseminar2019.space/?from=@
X-Served-By: Namecheap URL Forward

• http://www.tlsseminar2019.space/
198.54.117.210 No GZip used - 1904 / 5066 - 37.58 % possible
200

Html is minified: 179.45 %
0.390
H
small visible content (num chars: 492)
This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space 2019 Copyright. All Rights Reserved. The Sponsored Listings displayed above are served automatically by a third party. Neither Parkingcrew nor the domain owner maintain any relationship with the advertisers. Privacy Policy
Server: nginx
Date: Wed, 23 Oct 2019 13:44:37 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
X-CST: MISS,MISS
Allow: GET, HEAD

• http://www.tlsseminar2019.space/
198.54.117.211 No GZip used - 1904 / 5066 - 37.58 % possible
200

Html is minified: 179.45 %
0.376
H
small visible content (num chars: 492)
This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space 2019 Copyright. All Rights Reserved. The Sponsored Listings displayed above are served automatically by a third party. Neither Parkingcrew nor the domain owner maintain any relationship with the advertisers. Privacy Policy
Server: nginx
Date: Wed, 23 Oct 2019 13:44:37 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
X-CST: MISS,HIT
Allow: GET, HEAD

• http://www.tlsseminar2019.space/
198.54.117.212 No GZip used - 1904 / 5066 - 37.58 % possible
200

Html is minified: 179.45 %
0.377
H
small visible content (num chars: 492)
This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space 2019 Copyright. All Rights Reserved. The Sponsored Listings displayed above are served automatically by a third party. Neither Parkingcrew nor the domain owner maintain any relationship with the advertisers. Privacy Policy
Server: nginx
Date: Wed, 23 Oct 2019 13:44:37 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
X-CST: MISS,HIT
Allow: GET, HEAD

• http://www.tlsseminar2019.space/
198.54.117.215 No GZip used - 1904 / 5066 - 37.58 % possible
200

Html is minified: 179.45 %
0.380
H
small visible content (num chars: 492)
This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space 2019 Copyright. All Rights Reserved. The Sponsored Listings displayed above are served automatically by a third party. Neither Parkingcrew nor the domain owner maintain any relationship with the advertisers. Privacy Policy
Server: nginx
Date: Wed, 23 Oct 2019 13:44:38 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
X-CST: MISS,HIT
Allow: GET, HEAD

• http://www.tlsseminar2019.space/
198.54.117.216 No GZip used - 1904 / 5066 - 37.58 % possible
200

Html is minified: 179.45 %
0.380
H
small visible content (num chars: 492)
This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space 2019 Copyright. All Rights Reserved. The Sponsored Listings displayed above are served automatically by a third party. Neither Parkingcrew nor the domain owner maintain any relationship with the advertisers. Privacy Policy
Server: nginx
Date: Wed, 23 Oct 2019 13:44:38 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
X-CST: MISS,HIT
Allow: GET, HEAD

• http://www.tlsseminar2019.space/
198.54.117.217 No GZip used - 1904 / 5066 - 37.58 % possible
200

Html is minified: 179.45 %
0.370
H
small visible content (num chars: 492)
This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space 2019 Copyright. All Rights Reserved. The Sponsored Listings displayed above are served automatically by a third party. Neither Parkingcrew nor the domain owner maintain any relationship with the advertisers. Privacy Policy
Server: nginx
Date: Wed, 23 Oct 2019 13:44:39 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
X-CST: MISS,HIT
Allow: GET, HEAD

• http://www.tlsseminar2019.space/
198.54.117.218 No GZip used - 1904 / 5066 - 37.58 % possible
200

Html is minified: 179.45 %
0.373
H
small visible content (num chars: 492)
This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space This domain is registered at Namecheap This domain was recently registered at Namecheap. Please check back later! tlsseminar2019.space 2019 Copyright. All Rights Reserved. The Sponsored Listings displayed above are served automatically by a third party. Neither Parkingcrew nor the domain owner maintain any relationship with the advertisers. Privacy Policy
Server: nginx
Date: Wed, 23 Oct 2019 13:44:39 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
X-CST: MISS,HIT
Allow: GET, HEAD

• http://www.tlsseminar2019.space/?from=@

200

Html is minified: 179.45 %
0.416
H
Server: nginx
Date: Wed, 23 Oct 2019 13:45:15 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
X-CST: MISS,MISS
Allow: GET, HEAD

• https://tlsseminar2019.space/
162.255.119.38
-14

10.050
T
Timeout - The operation has timed out

• https://www.tlsseminar2019.space/
198.54.117.210
-2

1.544
V
ConnectFailure - Unable to connect to the remote server

• https://www.tlsseminar2019.space/
198.54.117.211
-2

1.533
V
ConnectFailure - Unable to connect to the remote server

• https://www.tlsseminar2019.space/
198.54.117.212
-2

1.540
V
ConnectFailure - Unable to connect to the remote server

• https://www.tlsseminar2019.space/
198.54.117.215
-2

1.540
V
ConnectFailure - Unable to connect to the remote server

• https://www.tlsseminar2019.space/
198.54.117.216
-14

10.043
T
Timeout - The operation has timed out

• https://www.tlsseminar2019.space/
198.54.117.217
-2

1.543
V
ConnectFailure - Unable to connect to the remote server

• https://www.tlsseminar2019.space/
198.54.117.218
-2

1.536
V
ConnectFailure - Unable to connect to the remote server

• http://tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
162.255.119.38
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
302
http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de?from=@
Html is minified: 101.55 %
0.374
D
Visible Content: Found .
Server: nginx
Date: Wed, 23 Oct 2019 13:45:09 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 131
Connection: close
Location: http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de?from=@
X-Served-By: Namecheap URL Forward

• http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
198.54.117.210
-8

0.716
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
198.54.117.211
-8

0.703
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
198.54.117.212
-8

0.700
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
198.54.117.215
-8

0.703
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
198.54.117.216
-8

0.707
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
198.54.117.217
-8

0.707
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
198.54.117.218
-8

0.694
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de?from=@

-8

0.690
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

7. Comments


1. General Results, most used to calculate the result

Aname "tlsseminar2019.space" is domain, public suffix is "space", top-level-domain-type is "generic", tld-manager is "DotSpace Inc."
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
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 - 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.
Dhttp://tlsseminar2019.space/ 162.255.119.38
302
http://www.tlsseminar2019.space/?from=@
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
Dhttp://tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 162.255.119.38
302
http://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de?from=@
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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
HFatal 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.
Khttps://www.tlsseminar2019.space/ 198.54.117.210, Status -2

https://www.tlsseminar2019.space/ 198.54.117.216, Status -14
Configuration problem - different ip addresses with different status
Khttps://www.tlsseminar2019.space/ 198.54.117.211, Status -2

https://www.tlsseminar2019.space/ 198.54.117.216, Status -14
Configuration problem - different ip addresses with different status
Khttps://www.tlsseminar2019.space/ 198.54.117.212, Status -2

https://www.tlsseminar2019.space/ 198.54.117.216, Status -14
Configuration problem - different ip addresses with different status
Khttps://www.tlsseminar2019.space/ 198.54.117.215, Status -2

https://www.tlsseminar2019.space/ 198.54.117.216, Status -14
Configuration problem - different ip addresses with different status
Khttps://www.tlsseminar2019.space/ 198.54.117.216, Status -14

https://www.tlsseminar2019.space/ 198.54.117.217, Status -2
Configuration problem - different ip addresses with different status
Khttps://www.tlsseminar2019.space/ 198.54.117.216, Status -14

https://www.tlsseminar2019.space/ 198.54.117.218, Status -2
Configuration problem - different ip addresses with different status
Vhttps://www.tlsseminar2019.space/ 198.54.117.210
-2

Connect failure - perhaps firewall
Vhttps://www.tlsseminar2019.space/ 198.54.117.211
-2

Connect failure - perhaps firewall
Vhttps://www.tlsseminar2019.space/ 198.54.117.212
-2

Connect failure - perhaps firewall
Vhttps://www.tlsseminar2019.space/ 198.54.117.215
-2

Connect failure - perhaps firewall
Vhttps://www.tlsseminar2019.space/ 198.54.117.217
-2

Connect failure - perhaps firewall
Vhttps://www.tlsseminar2019.space/ 198.54.117.218
-2

Connect failure - perhaps firewall

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


3. DNS- and NameServer - Checks

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: dns1.registrar-servers.com,dns2.registrar-servers.com
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: 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: d.nic.space: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (hivecast-2-defra.as15135.net Radix-D). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
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://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de?from=@
-8

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.54.117.210
-8

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.54.117.211
-8

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.54.117.212
-8

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.54.117.215
-8

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.54.117.216
-8

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.54.117.217
-8

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://www.tlsseminar2019.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.54.117.218
-8

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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.
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: 100077 milliseconds, 100.077 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

No CRT - CT-Log entries found


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:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
parkingpage.namecheap.com
0

no CAA entry found
1
0
www.tlsseminar2019.space



1
0
tlsseminar2019.space
0

no CAA entry found
1
0
namecheap.com
0

no CAA entry found
1
0
space
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tlsseminar2019.space

ok
1
0
www.tlsseminar2019.space


1
0
parkingpage.namecheap.com

ok
1
0
_acme-challenge.tlsseminar2019.space

Name Error - The domain name does not exist
1
0
_acme-challenge.www.tlsseminar2019.space

Name Error - The domain name does not exist
1
0
_acme-challenge.parkingpage.namecheap.com

Name Error - The domain name does not exist
1
0
_acme-challenge.tlsseminar2019.space.tlsseminar2019.space

Name Error - The domain name does not exist
1
0
_acme-challenge.www.tlsseminar2019.space.tlsseminar2019.space

Name Error - The domain name does not exist
1
0
_acme-challenge.www.tlsseminar2019.space.www.tlsseminar2019.space

Name Error - The domain name does not exist
1
0
_acme-challenge.parkingpage.namecheap.com.parkingpage.namecheap.com

Name Error - The domain name does not exist
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=318df154-57b8-492c-aac9-b4ae33f1df3b


Last Result: https://check-your-website.server-daten.de/?q=tlsseminar2019.space - 2019-10-23 15:43:49


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

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

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