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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
31.03.2021 09:07:39

Older results

T - 30.03.2021 14:42:41

T - 30.03.2021 10:59:22

T - 30.03.2021 10:38:24

T - 30.03.2021 09:59:55

T - 30.03.2021 09:32:29

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
tmappws.cz	A	109.238.218.212 Prague/Hlavni mesto Praha/Czechia (CZ) - PLANET Hostname: ip-109-238-218-212.aim-net.cz	yes	1	0
	AAAA		yes
www.tmappws.cz	A	109.238.218.212 Prague/Hlavni mesto Praha/Czechia (CZ) - PLANET Hostname: ip-109-238-218-212.aim-net.cz	yes	1	0
	AAAA		yes
*.tmappws.cz	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	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: cz
cz	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 20237, DigestType 2 and Digest z/Dz7NvFKcHwAxuhhAv7g1hTuSCe0eUI//SEUde3eOI=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner cz., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.04.2021, 20:00:00 +, Signature-Inception: 30.03.2021, 19: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 13, KeyTag 17014, Flags 256


	Public Key with Algorithm 13, KeyTag 20237, Flags 257 (SEP = Secure Entry Point)


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner cz., Algorithm: 13, 1 Labels, original TTL: 18000 sec, Signature-expiration: 13.04.2021, 21:56:26 +, Signature-Inception: 31.03.2021, 05:35:50 +, KeyTag 17014, Signer-Name: cz


	RRSIG-Owner cz., Algorithm: 13, 1 Labels, original TTL: 18000 sec, Signature-expiration: 03.04.2021, 00:00:00 +, Signature-Inception: 20.03.2021, 00:00:00 +, KeyTag 20237, Signer-Name: cz


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 17014 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 20237 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 20237, DigestType 2 and Digest "z/Dz7NvFKcHwAxuhhAv7g1hTuSCe0eUI//SEUde3eOI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: tmappws.cz
tmappws.cz	1 DS RR in the parent zone found


	DS with Algorithm 10, KeyTag 25536, DigestType 2 and Digest PtRIXWdQPtXKDPM/dbp7AgkjARkRR8d5aULMZ3MX7yA=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner tmappws.cz., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.04.2021, 18:35:29 +, Signature-Inception: 28.03.2021, 10:35:50 +, KeyTag 17014, Signer-Name: cz


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 17014 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 10, KeyTag 25536, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 10, KeyTag 59273, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner tmappws.cz., Algorithm: 10, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 25536, Signer-Name: tmappws.cz


	• Status: Good - Algorithmus 10 and DNSKEY with KeyTag 25536 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 10, KeyTag 25536, DigestType 2 and Digest "PtRIXWdQPtXKDPM/dbp7AgkjARkRR8d5aULMZ3MX7yA=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone


	RRSIG Type 1 validates the A - Result: 109.238.218.212 Validated: RRSIG-Owner tmappws.cz., Algorithm: 10, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "u8vfe65892136iftm2gccglcdpqf2ef8" equal the hashed NSEC3-owner "u8vfe65892136iftm2gccglcdpqf2ef8" and the hashed NextOwner "h0bhm2th8omumj09lf5hr9ef8og26bj2". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u8vfe65892136iftm2gccglcdpqf2ef8.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "u8vfe65892136iftm2gccglcdpqf2ef8" equal the hashed NSEC3-owner "u8vfe65892136iftm2gccglcdpqf2ef8" and the hashed NextOwner "h0bhm2th8omumj09lf5hr9ef8og26bj2". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u8vfe65892136iftm2gccglcdpqf2ef8.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "u8vfe65892136iftm2gccglcdpqf2ef8" equal the hashed NSEC3-owner "u8vfe65892136iftm2gccglcdpqf2ef8" and the hashed NextOwner "h0bhm2th8omumj09lf5hr9ef8og26bj2". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u8vfe65892136iftm2gccglcdpqf2ef8.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.tmappws.cz) sends a valid NSEC3 RR as result with the hashed owner name "u8vfe65892136iftm2gccglcdpqf2ef8" (unhashed: tmappws.cz). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "6qr5o1t4679ljq4puql3bi5hb6i4d4ej" (unhashed: *.tmappws.cz) with the owner "u8vfe65892136iftm2gccglcdpqf2ef8" and the NextOwner "h0bhm2th8omumj09lf5hr9ef8og26bj2". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u8vfe65892136iftm2gccglcdpqf2ef8.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "oqfh20nr2hmno9kosij4vckn1fdfra9t" (unhashed: _tcp.tmappws.cz) with the owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.tmappws.cz) sends a valid NSEC3 RR as result with the hashed query name "rqlvphthda4lto1i9f1nv9133q6ke5la" between the hashed NSEC3-owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the hashed NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So the zone confirmes the not-existence of that TLSA RR. Bitmap: A, RRSIG Validated: RRSIG-Owner h0bhm2th8omumj09lf5hr9ef8og26bj2.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "u8vfe65892136iftm2gccglcdpqf2ef8" equal the hashed NSEC3-owner "u8vfe65892136iftm2gccglcdpqf2ef8" and the hashed NextOwner "h0bhm2th8omumj09lf5hr9ef8og26bj2". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u8vfe65892136iftm2gccglcdpqf2ef8.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NoData-Proof required and found.

Zone: www.tmappws.cz
www.tmappws.cz	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 "h0bhm2th8omumj09lf5hr9ef8og26bj2" between the hashed NSEC3-owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the hashed NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, RRSIG Validated: RRSIG-Owner h0bhm2th8omumj09lf5hr9ef8og26bj2.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	RRSIG Type 1 validates the A - Result: 109.238.218.212 Validated: RRSIG-Owner www.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "h0bhm2th8omumj09lf5hr9ef8og26bj2" equal the hashed NSEC3-owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the hashed NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner h0bhm2th8omumj09lf5hr9ef8og26bj2.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "h0bhm2th8omumj09lf5hr9ef8og26bj2" equal the hashed NSEC3-owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the hashed NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner h0bhm2th8omumj09lf5hr9ef8og26bj2.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "h0bhm2th8omumj09lf5hr9ef8og26bj2" equal the hashed NSEC3-owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the hashed NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner h0bhm2th8omumj09lf5hr9ef8og26bj2.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.tmappws.cz) sends a valid NSEC3 RR as result with the hashed owner name "h0bhm2th8omumj09lf5hr9ef8og26bj2" (unhashed: www.tmappws.cz). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "o68j888j8sh1s4ne9pklf0g81vil4mod" (unhashed: _tcp.www.tmappws.cz) with the owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "r7l3vqql05j9cc5349nlvqc6ie36l753" (unhashed: *.www.tmappws.cz) with the owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.www.tmappws.cz) sends a valid NSEC3 RR as result with the hashed query name "nr0avu1v6nb8erd50hna2r8uov3blrd4" between the hashed NSEC3-owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the hashed NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So the zone confirmes the not-existence of that TLSA RR. Bitmap: A, RRSIG Validated: RRSIG-Owner h0bhm2th8omumj09lf5hr9ef8og26bj2.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "h0bhm2th8omumj09lf5hr9ef8og26bj2" equal the hashed NSEC3-owner "h0bhm2th8omumj09lf5hr9ef8og26bj2" and the hashed NextOwner "u8vfe65892136iftm2gccglcdpqf2ef8". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner h0bhm2th8omumj09lf5hr9ef8og26bj2.tmappws.cz., Algorithm: 10, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.04.2021, 08:38:01 +, Signature-Inception: 30.03.2021, 07:08:01 +, KeyTag 59273, Signer-Name: tmappws.cz


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.tmappws.cz	• ns.forpsi.net / dns-slave1.forpsi.org		•
tmappws.cz	• ns.forpsi.cz / dns-slave2.forpsi.org	81.2.209.185 Ktis/Jihocesky kraj/Czechia (CZ) - INTERNET CZ	•
	•	2001:15e8:201:1::d1b9 Ktis/Jihocesky kraj/Czechia (CZ) - INTERNET CZ	•
	• ns.forpsi.it / dns-slave3.forpsi.org	95.110.254.165 Arezzo/Tuscany/Italy (IT) - Aruba S.p.A. Network	•
	•	2a00:6d41:2:1::5 Arezzo/Tuscany/Italy (IT) - Aruba S.p.A. Network	•
	• ns.forpsi.net / dns-slave1.forpsi.org	81.2.194.130 Ktis/Jihocesky kraj/Czechia (CZ) - INTERNET CZ	•
	•	2001:15e8:101:1::c282 Ktis/Jihocesky kraj/Czechia (CZ) - INTERNET CZ	•
cz	• a.ns.nic.cz / dns-b-10.nic.cz		•
	• b.ns.nic.cz / dns-b-02.nic.cz		•
	• c.ns.nic.cz / dns-linx-dns03.nic.cz		•
	• d.ns.nic.cz / dns-b-01.nic.cz		•

4. SOA-Entries

Domain:	cz
Zone-Name:	cz
Primary:	a.ns.nic.cz
Mail:	hostmaster.nic.cz
Serial:	1617172550
Refresh:	900
Retry:	300
Expire:	604800
TTL:	900
num Entries:	4

Domain:	tmappws.cz
Zone-Name:	tmappws.cz
Primary:	ns.forpsi.net
Mail:	admin.forpsi.com
Serial:	2021033001
Refresh:	14400
Retry:	3600
Expire:	2592000
TTL:	3600
num Entries:	6

Domain:	www.tmappws.cz
Zone-Name:	tmappws.cz
Primary:	ns.forpsi.net
Mail:	admin.forpsi.com
Serial:	2021033001
Refresh:	14400
Retry:	3600
Expire:	2592000
TTL:	3600
num Entries:	1

5. Screenshots

Startaddress: https://tmappws.cz, address used: https://tmappws.cz/, Screenshot created 2021-04-04 11:17:07 +00:0

Mobil (412px x 732px)

519 milliseconds

Mobil + Landscape (732px x 412px)

456 milliseconds

Screenshot mobile landscape - https://tmappws.cz/

Screen (1280px x 1680px)

3875 milliseconds

Screenshot Desktop - https://tmappws.cz/

Mobile- and other Chrome-Checks

	width	height
visual Viewport	412	732
content Size	412	732

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, X25519, and AES_128_GCM.

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://tmappws.cz/ 109.238.218.212	200	Html is minified: 109.76 %	0.060	H
small visible content (num chars: 14) Index of / ../
Server: nginx/1.18.0 (Ubuntu)
Date: Wed, 31 Mar 2021 07:08:15 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• http://www.tmappws.cz/ 109.238.218.212	200	Html is minified: 109.76 %	3.060	H
small visible content (num chars: 14) Index of / ../
Server: nginx/1.18.0 (Ubuntu)
Date: Wed, 31 Mar 2021 07:08:18 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://tmappws.cz/ 109.238.218.212 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	200	Html is minified: 109.76 % Other inline scripts (∑/total): 0/0	23.414	B
small visible content (num chars: 14) Index of / ../
Server: nginx/1.18.0 (Ubuntu)
Date: Wed, 31 Mar 2021 07:08:21 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://www.tmappws.cz/ 109.238.218.212	-14		10.033	T
Timeout - The operation has timed out

• http://tmappws.cz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.238.218.212 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 109.46 % Other inline scripts (∑/total): 0/0	0.063	A
Not Found
Visible Content: 404 Not Found nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Wed, 31 Mar 2021 07:08:53 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• http://www.tmappws.cz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.238.218.212 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 109.46 % Other inline scripts (∑/total): 0/0	3.070	A
Not Found
Visible Content: 404 Not Found nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Wed, 31 Mar 2021 07:08:56 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://109.238.218.212/ 109.238.218.212	-1		45.297	U
Interner Fehler: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 109.238.218.212:443

7. Comments

	1. General Results, most used to calculate the result
A	name "tmappws.cz" is domain, public suffix is ".cz", top-level-domain is ".cz", top-level-domain-type is "country-code", Country is Czechia, tld-manager is "CZ.NIC, z.s.p.o", num .cz-domains preloaded: 1308 (complete: 151507)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: tmappws.cz has only one ip address.
	Warning: Only one ip address found: www.tmappws.cz 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: tmappws.cz has no ipv6 address.
	Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.tmappws.cz has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	Good: one preferred version: non-www is preferred
A	Good: No cookie sent via http.
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (5 urls)
	http://tmappws.cz/ 109.238.218.212			Url with incomplete Content-Type - header - missing charset
	http://www.tmappws.cz/ 109.238.218.212			Url with incomplete Content-Type - header - missing charset
	https://tmappws.cz/ 109.238.218.212			Url with incomplete Content-Type - header - missing charset
	http://tmappws.cz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.238.218.212			Url with incomplete Content-Type - header - missing charset
	http://www.tmappws.cz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.238.218.212			Url with incomplete Content-Type - header - missing charset
B	https://tmappws.cz/ 109.238.218.212	200		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.
	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 tmappws.cz, 1 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.tmappws.cz, 1 ip addresses.
	2. Header-Checks
	3. DNS- and NameServer - Checks
A	Info:: 6 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
A	Info:: 6 Queries complete, 6 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
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.ns.forpsi.cz (2001:15e8:201:1::d1b9, 81.2.209.185), ns.forpsi.it (2a00:6d41:2:1::5, 95.110.254.165), ns.forpsi.net (81.2.194.130)
A	Good (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 3 different Name Servers found: ns.forpsi.cz, ns.forpsi.it, ns.forpsi.net, 3 Name Servers included in Delegation: ns.forpsi.cz, ns.forpsi.it, ns.forpsi.net, 3 Name Servers included in 1 Zone definitions: ns.forpsi.cz, ns.forpsi.it, ns.forpsi.net, 1 Name Servers listed in SOA.Primary: ns.forpsi.net.
A	Good: Only one SOA.Primary Name Server found.: ns.forpsi.net.
A	Good: SOA.Primary Name Server included in the delegation set.: ns.forpsi.net.
A	Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns.forpsi.cz, ns.forpsi.it, ns.forpsi.net
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 3 different Name Servers found
A	Good: Name servers with different Top Level Domains / Public Suffix List entries found: 3 Name Servers, 3 Top Level Domains: it, cz, net
A	Good: Name Servers with different domain names found.: 3 different Domains found
A	Good: Name servers with different Country locations found: 3 Name Servers, 2 Countries: CZ, IT
A	Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 81., 95., 2 different subnets (first two Bytes): 81.2., 95.110., 3 different subnets (first three Bytes): 81.2.194., 81.2.209., 95.110.254.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2a00:, 2 different subnets (first two blocks): 2001:15e8:, 2a00:6d41:, 3 different subnets (first three blocks): 2001:15e8:0101:, 2001:15e8:0201:, 2a00:6d41:0002:, 3 different subnets (first four blocks): 2001:15e8:0101:0001:, 2001:15e8:0201:0001:, 2a00:6d41:0002:0001:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 6 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 6 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
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
A	Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Good: No https + http status 200 with inline CSS / JavaScript found
A	Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
	https://tmappws.cz/ 109.238.218.212	200		Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
A	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
	http://www.tmappws.cz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.238.218.212	404	3.070 seconds	Warning: 404 needs more then one second
A	Duration: 153490 milliseconds, 153.490 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

tmappws.cz

109.238.218.212

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

tmappws.cz

109.238.218.212

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

no http/2 via ALPN

Tls.1.2
no Tls.1.1
no Tls.1.0

no http/2 via ALPN

Tls.1.2
no Tls.1.1
no Tls.1.0

Chain - incomplete	1	CN=tmappws.cz
	2	CN=R3, O=Let's Encrypt, C=US

9. Certificates

CN=tmappws.cz

30.03.2021

28.06.2021
1455 days expired

tmappws.cz - 1 entry

CN=tmappws.cz

30.03.2021

28.06.2021
1455 days expired

tmappws.cz - 1 entry

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	044273A4E35F12CB1765B923887B65381653
Thumbprint:	475A3D6598F13E8623D671710E603D3627F1FCF6
SHA256 / Certificate:	Dg4n7JahvGNN81Vee9I1T76/HtNvQp1fHrO86BQ0hmU=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	4c29814c493930b8f17eba0d875857551ad686db2d3a17f80de85a93d1292991
SHA256 hex / Subject Public Key Information (SPKI):	4c29814c493930b8f17eba0d875857551ad686db2d3a17f80de85a93d1292991
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://r3.o.lencr.org
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=R3, O=Let's Encrypt, C=US

07.10.2020

29.09.2021
1362 days expired

CN=R3, O=Let's Encrypt, C=US

07.10.2020

29.09.2021
1362 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	400175048314A4C8218C84A90C16CDDF
Thumbprint:	48504E974C0DAC5B5CD476C8202274B24C8C7172
SHA256 / Certificate:	cwwb3NhfV85dwLunM+XxulqSWyp3HWQKJvekVCJNrTs=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1361 days expired

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1361 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA-1 with RSA Encryption
Serial Number:	44AFB080D6A327BA893039862EF8406B
Thumbprint:	DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:	BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):	0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

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

Summary

No data found or small Code-update

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns.forpsi.cz, ns.forpsi.it, ns.forpsi.net

QNr.	Domain	Type	NS used
1	cz	NS	k.root-servers.net (2001:7fd::1)
	Answer: a.ns.nic.cz, b.ns.nic.cz, c.ns.nic.cz, d.ns.nic.cz
2	ns.forpsi.cz: 2001:15e8:201:1::d1b9, 81.2.209.185	NS	a.ns.nic.cz (2001:678:f::1)
3	it	NS	a.root-servers.net (2001:503:ba3e::2:30)
	Answer: a.dns.it, dns.nic.it, m.dns.it, nameserver.cnr.it, r.dns.it, s.dns.it
4	ns.forpsi.it: 2a00:6d41:2:1::5, 95.110.254.165	NS	a.dns.it (2001:678:12:0:194:0:16:215)
5	net	NS	g.root-servers.net (2001:500:12::d0d)
	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
6	ns.forpsi.net: 81.2.194.130	NS	a.gtld-servers.net (2001:503:a83e::2:30)

14. CAA - Entries

Domainname	Value	∑ Queries
www.tmappws.cz	no CAA entry found	1
tmappws.cz	no CAA entry found	1
cz	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
tmappws.cz	ok	1
www.tmappws.cz	ok	1
_acme-challenge.tmappws.cz	Name Error - The domain name does not exist	1
_acme-challenge.www.tmappws.cz	Name Error - The domain name does not exist	1
_acme-challenge.tmappws.cz.tmappws.cz	Name Error - The domain name does not exist	1
_acme-challenge.www.tmappws.cz.tmappws.cz	Name Error - The domain name does not exist	1
_acme-challenge.www.tmappws.cz.www.tmappws.cz	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=8633b691-2cee-4336-9ccc-e1d7f8bd8ced

Last Result: https://check-your-website.server-daten.de/?q=tmappws.cz - 2021-04-04 11:15:00

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

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

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

QR-Code of this page - https://check-your-website.server-daten.de/?d=tmappws.cz

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

Older results

1. IP-Addresses

2. DNSSEC

3. Name Servers

4. SOA-Entries

5. Screenshots

Mobile- and other Chrome-Checks

6. Url-Checks

7. Comments

1. General Results, most used to calculate the result

2. Header-Checks

3. DNS- and NameServer - Checks

4. Content- and Performance-critical Checks

8. Connections

9. Certificates

10. Last Certificates - Certificate Transparency Log Check

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

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

11. Html-Content - Entries

Summary

Details (currently limited to 500 rows - some problems with spam users)

12. Html-Parsing via https://validator.w3.org/nu/

13. Nameserver - IP-Adresses

14. CAA - Entries

15. TXT - Entries

16. DomainService - Entries

17. Cipher Suites

18. Portchecks