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

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
20.11.2023 18:35:13

Older results

X - 18.10.2023 11:03:18

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
twnet.dedyn.io	A	83.7.12.236 Racibórz/Silesia/Poland (PL) - Orange Polska Spolka Akcyjna Hostname: abea236.neoplus.adsl.tpnet.pl	yes	2	0
	AAAA		yes
www.twnet.dedyn.io	CNAME	twnet.dedyn.io	yes	1	0
	A	83.7.12.236 Racibórz/Silesia/Poland (PL) - Orange Polska Spolka Akcyjna Hostname: abea236.neoplus.adsl.tpnet.pl	yes
*.twnet.dedyn.io	A	83.7.12.236	yes
	A	83.7.12.236	yes
	AAAA		yes
	AAAA		yes
	CNAME	twnet.dedyn.io	yes
	CNAME	twnet.dedyn.io	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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 46780, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 57355, DigestType 2 and Digest laV8O6t4SdvN33xyracaiBRrFBEQMYylvmcgV+hlw+I=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.12.2023, 05:00:00 +, Signature-Inception: 20.11.2023, 04:00:00 +, KeyTag 46780, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 41901, Flags 256


	Public Key with Algorithm 8, KeyTag 45783, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 10.12.2023, 03:14:27 +, Signature-Inception: 19.11.2023, 02:14:27 +, KeyTag 57355, Signer-Name: io


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


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

Zone: dedyn.io
dedyn.io	2 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 35233, DigestType 2 and Digest nGcq4ySIT5oBdDMMp2RPaWAXLB2UAj+Ub3B2Ob5tOrA=


	DS with Algorithm 13, KeyTag 35233, DigestType 4 and Digest zoB+diKdZKrohrJzI1W91o4snRA5YJCF3+FZM/4DHHGYGn+nf0WyIZL3ZySpsp+5


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner dedyn.io., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.12.2023, 03:14:27 +, Signature-Inception: 19.11.2023, 02:14:27 +, KeyTag 41901, Signer-Name: io


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


	1 DNSKEY RR found


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner dedyn.io., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 35233, Signer-Name: dedyn.io


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 35233, DigestType 2 and Digest "nGcq4ySIT5oBdDMMp2RPaWAXLB2UAj+Ub3B2Ob5tOrA=" 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 13, KeyTag 35233, DigestType 4 and Digest "zoB+diKdZKrohrJzI1W91o4snRA5YJCF3+FZM/4DHHGYGn+nf0WyIZL3ZySpsp+5" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: twnet.dedyn.io
twnet.dedyn.io	2 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 49980, DigestType 2 and Digest HSYVAr6WEvce7lio9/rLspW6jDd5/RHbn5Kv+6zOaW8=


	DS with Algorithm 13, KeyTag 49980, DigestType 4 and Digest aHjQbwMkB+t1h2jkH02orDuqkWGyDpBRHuLR2GmbrsSo9NHzhTuWoYxyVLtAYAkJ


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner twnet.dedyn.io., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 35233, Signer-Name: dedyn.io


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


	1 DNSKEY RR found


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner twnet.dedyn.io., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 49980, DigestType 2 and Digest "HSYVAr6WEvce7lio9/rLspW6jDd5/RHbn5Kv+6zOaW8=" 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 13, KeyTag 49980, DigestType 4 and Digest "aHjQbwMkB+t1h2jkH02orDuqkWGyDpBRHuLR2GmbrsSo9NHzhTuWoYxyVLtAYAkJ" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone


	RRSIG Type 1 validates the A - Result: 83.7.12.236 Validated: RRSIG-Owner twnet.dedyn.io., Algorithm: 13, 3 Labels, original TTL: 60 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	RRSIG Type 5 validates the TLSA - Result (_443._tcp.twnet.dedyn.io): twnet.dedyn.io. That's a CNAME answer. RRSIG Owner has 5 labels, RRSIG Labels = 3, so it's a wildcard expansion, the Query Name doesn't exists. An additional NSEC/NSEC3 is required to confirm the Not-Existence of the query name. Validated: RRSIG-Owner _443._tcp.twnet.dedyn.io., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	RRSIG Type 257 validates the CAA - Result: 5\|issueletsencrypt.org Validated: RRSIG-Owner twnet.dedyn.io., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "ck2pl10al0hp07amhklpgadcdq6jak7p" equal the hashed NSEC3-owner "ck2pl10al0hp07amhklpgadcdq6jak7p" and the hashed NextOwner "65frd99n5lajrk3b9eknjukcac07m5g5". 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, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner ck2pl10al0hp07amhklpgadcdq6jak7p.twnet.dedyn.io., Algorithm: 13, 4 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "ck2pl10al0hp07amhklpgadcdq6jak7p" equal the hashed NSEC3-owner "ck2pl10al0hp07amhklpgadcdq6jak7p" and the hashed NextOwner "65frd99n5lajrk3b9eknjukcac07m5g5". 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, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner ck2pl10al0hp07amhklpgadcdq6jak7p.twnet.dedyn.io., Algorithm: 13, 4 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "ck2pl10al0hp07amhklpgadcdq6jak7p" equal the hashed NSEC3-owner "ck2pl10al0hp07amhklpgadcdq6jak7p" and the hashed NextOwner "65frd99n5lajrk3b9eknjukcac07m5g5". 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, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner ck2pl10al0hp07amhklpgadcdq6jak7p.twnet.dedyn.io., Algorithm: 13, 4 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.twnet.dedyn.io) sends a valid NSEC3 RR as result with the hashed owner name "ck2pl10al0hp07amhklpgadcdq6jak7p" (unhashed: twnet.dedyn.io). 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 "d2aej1h227rtngujfus64o2edsumlqmj" (unhashed: _tcp.twnet.dedyn.io) with the owner "ck2pl10al0hp07amhklpgadcdq6jak7p" and the NextOwner "65frd99n5lajrk3b9eknjukcac07m5g5". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.twnet.dedyn.io) sends a valid NSEC3 RR as result with the owner name "ck2pl10al0hp07amhklpgadcdq6jak7p" greater the NextOwner-Name "65frd99n5lajrk3b9eknjukcac07m5g5", so the NSEC3 covers the end of the zone. The hashed query name "2vvpt58olslvtimt7aqsttros2ic9vde" comes before the hashed NextOwner, so the zone confirmes the not-existence of that TLSA RR. Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner ck2pl10al0hp07amhklpgadcdq6jak7p.twnet.dedyn.io., Algorithm: 13, 4 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	Status: Good. NoData-Proof required and found.

Zone: www.twnet.dedyn.io
www.twnet.dedyn.io	2 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 49980, DigestType 2 and Digest HSYVAr6WEvce7lio9/rLspW6jDd5/RHbn5Kv+6zOaW8=


	DS with Algorithm 13, KeyTag 49980, DigestType 4 and Digest aHjQbwMkB+t1h2jkH02orDuqkWGyDpBRHuLR2GmbrsSo9NHzhTuWoYxyVLtAYAkJ


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner twnet.dedyn.io., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 35233, Signer-Name: dedyn.io


	• not checked


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck2pl10al0hp07amhklpgadcdq6jak7p" as Owner. That's the Hash of "twnet.dedyn.io" with the NextHashedOwnerName "65frd99n5lajrk3b9eknjukcac07m5g5". So that domain name is the Closest Encloser of "www.twnet.dedyn.io". Opt-Out: False. Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner ck2pl10al0hp07amhklpgadcdq6jak7p.twnet.dedyn.io., Algorithm: 13, 4 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	The ClosestEncloser says, that "*.twnet.dedyn.io" with the Hash "65frd99n5lajrk3b9eknjukcac07m5g5" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "ck2pl10al0hp07amhklpgadcdq6jak7p" and the Next Owner "65frd99n5lajrk3b9eknjukcac07m5g5", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False. Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner ck2pl10al0hp07amhklpgadcdq6jak7p.twnet.dedyn.io., Algorithm: 13, 4 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	RRSIG Type 5 validates the CNAME - Result: twnet.dedyn.io. RRSIG Owner has 4 labels, RRSIG Labels = 3, so it's a wildcard expansion, the Query Name doesn't exists. An additional NSEC/NSEC3 is required to confirm the Not-Existence of the query name. Validated: RRSIG-Owner www.twnet.dedyn.io., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "ck2pl10al0hp07amhklpgadcdq6jak7p" (unhashed: twnet.dedyn.io). So that's the Closest Encloser of the query name. CNAME-Query sends a valid NSEC3 RR as result with the owner name "ck2pl10al0hp07amhklpgadcdq6jak7p" greater the NextOwner-Name "65frd99n5lajrk3b9eknjukcac07m5g5", so the NSEC3 covers the end of the zone. The hashed query name "umldukcf760krcstk5v6n46hddb0e2cq" comes after the hashed Owner, so the zone confirmes the not-existence of that CNAME RR. Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner ck2pl10al0hp07amhklpgadcdq6jak7p.twnet.dedyn.io., Algorithm: 13, 4 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2023, 00:00:00 +, Signature-Inception: 09.11.2023, 00:00:00 +, KeyTag 49980, Signer-Name: twnet.dedyn.io


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
twnet.dedyn.io	U get.desec.io	88.99.64.5 Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH	•
	U	2a01:4f8:10a:1044:deec:642:ac10:80 Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH
	• ns1.desec.io / 1061eca8ae69	45.54.76.1 Dallas/Texas/United States (US) - NetActuate, Inc	•
	•	2607:f740:e633:deec::2 New York/United States (US) - NetActuate, Inc	•
	• ns2.desec.org / 0eee616d37e9	157.53.224.1 Raleigh/North Carolina/United States (US) - NetActuate, Inc	•
	•	2607:f740:e00a:deec::2 New York/United States (US) - NetActuate, Inc	•
dedyn.io	• get.desec.io
	• ns1.desec.io / 1061eca8ae69	45.54.76.1 Dallas/Texas/United States (US) - NetActuate, Inc	•
	•	2607:f740:e633:deec::2 New York/United States (US) - NetActuate, Inc	•
	• ns2.desec.org / 0eee616d37e9	157.53.224.1 Raleigh/North Carolina/United States (US) - NetActuate, Inc	•
	•	2607:f740:e00a:deec::2 New York/United States (US) - NetActuate, Inc	•
io	• a0.nic.io / app20.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• a2.nic.io / FRA3		•
	• b0.nic.io / app15.ams2.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• c0.nic.io / app30.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•

4. SOA-Entries

Domain:	io
Zone-Name:	io
Primary:	a0.nic.io
Mail:	hostmaster.donuts.email
Serial:	1700501262
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	4

Domain:	dedyn.io
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	dedyn.io
Zone-Name:	dedyn.io
Primary:	get.desec.io
Mail:	get.desec.io
Serial:	2023114882
Refresh:	86400
Retry:	3600
Expire:	2419200
TTL:	3600
num Entries:	4

Domain:	twnet.dedyn.io
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	2

Domain:	twnet.dedyn.io
Zone-Name:	twnet.dedyn.io
Primary:	get.desec.io
Mail:	get.desec.io
Serial:	2023114812
Refresh:	86400
Retry:	3600
Expire:	2419200
TTL:	3600
num Entries:	4

5. Screenshots

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

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://twnet.dedyn.io/ 83.7.12.236	307	http://twnet.dedyn.io/cosmos-ui Html is minified: 104.55 %	0.140	D
Content-Type: text/html; charset=utf-8
Location: /cosmos-ui
Date: Mon, 20 Nov 2023 17:36:31 GMT
Content-Length: 46
Connection: close

• http://www.twnet.dedyn.io/ 83.7.12.236	307	http://www.twnet.dedyn.io/cosmos-ui Html is minified: 104.55 %	0.140	D
Content-Type: text/html; charset=utf-8
Location: /cosmos-ui
Date: Mon, 20 Nov 2023 17:36:31 GMT
Content-Length: 46
Connection: close

• http://twnet.dedyn.io/cosmos-ui	200	Html is minified: 143.51 %	0.144	H
Accept-Ranges: bytes
Content-Length: 630
Content-Type: text/html; charset=utf-8
Last-Modified: Wed, 15 Nov 2023 15:52:20 GMT
Date: Mon, 20 Nov 2023 17:36:35 GMT
Connection: close

• http://www.twnet.dedyn.io/cosmos-ui	400	Html is minified: 100.00 %	0.140	M
Bad Request
Date: Mon, 20 Nov 2023 17:36:35 GMT
Content-Length: 128
Content-Type: text/plain; charset=utf-8
Connection: close

• https://twnet.dedyn.io/ 83.7.12.236	-2		1.203	V
ConnectFailure - Unable to connect to the remote server

• https://www.twnet.dedyn.io/ 83.7.12.236	-2		1.203	V
ConnectFailure - Unable to connect to the remote server

• http://twnet.dedyn.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 83.7.12.236 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	0.144	A
Not Found
Visible Content: 404 page not found
Content-Type: text/plain; charset=utf-8
X-Content-Type-Options: nosniff
Date: Mon, 20 Nov 2023 17:36:33 GMT
Content-Length: 19
Connection: close

• http://www.twnet.dedyn.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 83.7.12.236 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	0.124	A
Not Found
Visible Content: 404 page not found
Content-Type: text/plain; charset=utf-8
X-Content-Type-Options: nosniff
Date: Mon, 20 Nov 2023 17:36:34 GMT
Content-Length: 19
Connection: close

• https://83.7.12.236/ 83.7.12.236	-2		1.217	V
ConnectFailure - Unable to connect to the remote server

7. Comments

	1. General Results, most used to calculate the result
A	name "twnet.dedyn.io" is domain, public suffix is ".dedyn.io", top-level-domain is ".io", top-level-domain-type is "country-code", Country is British Indian Ocean Territory (the), tld-manager is "IO Top Level Domain Registry", num .io-domains preloaded: 2306 (complete: 231048)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: twnet.dedyn.io has only one ip address.
	Warning: Only one ip address found: www.twnet.dedyn.io 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: twnet.dedyn.io 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.twnet.dedyn.io has no ipv6 address.
A	Good - only one version with Http-Status 200
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
D	http://twnet.dedyn.io/ 83.7.12.236	307	http://twnet.dedyn.io/cosmos-ui	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.
D	http://www.twnet.dedyn.io/ 83.7.12.236	307	http://www.twnet.dedyn.io/cosmos-ui	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.
H	Fatal error: No https - result with http-status 200, no encryption
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.
M	http://www.twnet.dedyn.io/cosmos-ui	400		Misconfiguration - main pages should never send http status 400 - 499
V	https://twnet.dedyn.io/ 83.7.12.236	-2		Connect failure - perhaps firewall
V	https://www.twnet.dedyn.io/ 83.7.12.236	-2		Connect failure - perhaps firewall
V	https://83.7.12.236/ 83.7.12.236	-2		Connect failure - perhaps firewall
X	Fatal error: Nameserver isn't defined or has timeout
X	Fatal error: Nameserver doesn't support TCP connection: get.desec.io / 2a01:4f8:10a:1044:deec:642:ac10:80: Timeout
	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 twnet.dedyn.io, 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.twnet.dedyn.io, 1 ip addresses.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.twnet.dedyn.io
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
U				No https result with http status 2 or 4 (standard-check) found, no header checked.
	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.ns2.desec.org (157.53.224.1, 2607:f740:e00a:deec::2), ns1.desec.io (2607:f740:e633:deec::2, 45.54.76.1)
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: get.desec.io, ns1.desec.io, ns2.desec.org, 2 Name Servers included in Delegation: ns1.desec.io, ns2.desec.org, 2 Name Servers included in 2 Zone definitions: ns1.desec.io, ns2.desec.org, 1 Name Servers listed in SOA.Primary: get.desec.io.
A	Good: Only one SOA.Primary Name Server found.: get.desec.io.
	Error: SOA.Primary Name Server not included in the delegation set.: get.desec.io.
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, 2 Top Level Domains: io, org
A	Good: Name Servers with different domain names found.: 2 different Domains found
A	Good: Name servers with different Country locations found: 3 Name Servers, 2 Countries: DE, US
A	Info: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 157., 45., 88., 3 different subnets (first two Bytes): 157.53., 45.54., 88.99., 3 different subnets (first three Bytes): 157.53.224., 45.54.76., 88.99.64.
A	Excellent: Every Name Server IPv4-address starts with an unique Byte.
A	Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2607:, 2a01:, 2 different subnets (first two blocks): 2607:f740:, 2a01:04f8:, 3 different subnets (first three blocks): 2607:f740:e00a:, 2607:f740:e633:, 2a01:04f8:010a:, 3 different subnets (first four blocks): 2607:f740:e00a:deec:, 2607:f740:e633:deec:, 2a01:04f8:010a:1044:
A	Good: Name Server IPv6 addresses from different subnets found.
	Nameserver doesn't pass all EDNS-Checks: get.desec.io: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
	Nameserver doesn't pass all EDNS-Checks: get.desec.io / 88.99.64.5: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: get.desec.io / 2a01:4f8:10a:1044:deec:642:ac10:80: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns1.desec.io / 45.54.76.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (1061eca8ae69). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns1.desec.io / 45.54.76.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (1061eca8ae69). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns1.desec.io / 2607:f740:e633:deec::2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (1061eca8ae69). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns1.desec.io / 2607:f740:e633:deec::2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (1061eca8ae69). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns2.desec.org / 157.53.224.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (0eee616d37e9). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns2.desec.org / 157.53.224.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (0eee616d37e9). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns2.desec.org / 2607:f740:e00a:deec::2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (0eee616d37e9). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns2.desec.org / 2607:f740:e00a:deec::2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (0eee616d37e9). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
A	Good: All SOA have the same Serial Number
A	Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
	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	Info: No img element found, no alt attribute checked
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 104770 milliseconds, 104.770 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)

Issuer				last 7 days	active	num Certs
CN=R3, O=Let's Encrypt, C=US				0	0	3

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
6037366004 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-10-19 18:00:11	2024-01-17 18:00:10	*.twnet.dedyn.io, twnet.dedyn.io - 2 entries
6026314900 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-10-17 19:26:02	2024-01-15 19:26:01	twnet.dedyn.io - 1 entries
5987828839 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-10-10 19:02:29	2024-01-08 19:02:28	*.twnet.dedyn.io, twnet.dedyn.io - 2 entries

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

Issuer				last 7 days	active	num Certs
CN=R3, O=Let's Encrypt, C=US				0 /0 new	0	3

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
10834834682 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-10-19 16:00:11	2024-01-17 17:00:10	*.twnet.dedyn.io, twnet.dedyn.io 2 entries
10815114524 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-10-17 17:26:02	2024-01-15 18:26:01	twnet.dedyn.io 1 entries
10711287676 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-10-10 17:02:29	2024-01-08 18:02:28	*.twnet.dedyn.io, twnet.dedyn.io 2 entries

11. Html-Content - Entries

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

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: get.desec.io, ns1.desec.io, ns2.desec.org

QNr.	Domain	Type	NS used
1	io	NS	f.root-servers.net (2001:500:2f::f)
	Answer: a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io
2	get.desec.io	NS	a0.nic.io (2a01:8840:9e::17)
	Answer: ns1.desec.io, ns2.desec.org
	Answer: ns1.desec.io 2607:f740:e633:deec::2, 45.54.76.1
3	org	NS	l.root-servers.net (2001:500:9f::42)
	Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
4	ns2.desec.org: 157.53.224.1, 2607:f740:e00a:deec::2	NS	a0.org.afilias-nst.info (2001:500:e::1)
5	get.desec.io: 88.99.64.5	A	ns1.desec.io (2607:f740:e633:deec::2)
6	get.desec.io: 2a01:4f8:10a:1044:deec:642:ac10:80	AAAA	ns1.desec.io (2607:f740:e633:deec::2)

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries
www.twnet.dedyn.io	5	issue	letsencrypt.org	1
twnet.dedyn.io	5	issue	letsencrypt.org	1
dedyn.io	0		no CAA entry found	1
io	0		no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
twnet.dedyn.io	ok	1
www.twnet.dedyn.io		1
_acme-challenge.twnet.dedyn.io		1
_acme-challenge.www.twnet.dedyn.io		1
_acme-challenge.twnet.dedyn.io.twnet.dedyn.io		1
_acme-challenge.www.twnet.dedyn.io.twnet.dedyn.io		1
_acme-challenge.www.twnet.dedyn.io.www.twnet.dedyn.io		1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No results

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=f6834c9b-cfa3-4b49-9d8a-d0b32cf3ad22

Last Result: https://check-your-website.server-daten.de/?q=twnet.dedyn.io - 2023-11-20 18:35:13

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

<a href="https://check-your-website.server-daten.de/?q=twnet.dedyn.io" target="_blank">Check this Site: twnet.dedyn.io</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=twnet.dedyn.io