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:
18.03.2023 18:49:21

Older results

V - 18.03.2023 18:37:02

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
qleroy.xyz	A	162.19.74.199 Paris/Île-de-France/France (FR) - OVH SAS Hostname: vps-a47f8247.vps.ovh.net	yes	1	0
	AAAA		yes
www.qleroy.xyz	A		yes	1	0
	AAAA		yes
*.qleroy.xyz	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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 951, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 3599, DigestType 1 and Digest P6OyZPRdtfOL7erxqIt2qjGMLH8=


	DS with Algorithm 8, KeyTag 3599, DigestType 2 and Digest uXM4abyEyGu1nRArpdprJ7IIhVIzKjnc1UvE6NZrBJk=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner xyz., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.03.2023, 05:00:00 +, Signature-Inception: 18.03.2023, 04:00:00 +, KeyTag 951, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 53358, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner xyz., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 16.04.2023, 07:09:10 +, Signature-Inception: 17.03.2023, 07:54:24 +, KeyTag 3599, Signer-Name: xyz


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 3599, DigestType 1 and Digest "P6OyZPRdtfOL7erxqIt2qjGMLH8=" 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 3599, DigestType 2 and Digest "uXM4abyEyGu1nRArpdprJ7IIhVIzKjnc1UvE6NZrBJk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: qleroy.xyz
qleroy.xyz	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 8956, DigestType 2 and Digest VBBTSNTm26D2SXKGssOur8aEgeTeBgcdFguovdTciow=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner qleroy.xyz., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 28.03.2023, 00:32:08 +, Signature-Inception: 25.02.2023, 17:47:32 +, KeyTag 53358, Signer-Name: xyz


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 39003, Flags 256


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner qleroy.xyz., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 8956, Signer-Name: qleroy.xyz


	RRSIG-Owner qleroy.xyz., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


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


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


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


	RRSIG Type 1 validates the A - Result: 162.19.74.199 Validated: RRSIG-Owner qleroy.xyz., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	RRSIG Type 16 validates the TXT - Result: 1\|www.qleroy.xyz v=spf1 include:mx.ovh.com ~all Validated: RRSIG-Owner qleroy.xyz., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "uee489ob5dcspgijmjhh9larkknfkab1" equal the hashed NSEC3-owner "uee489ob5dcspgijmjhh9larkknfkab1" and the hashed NextOwner "7nbfsioio9lampj987tk4mgengff5omg". 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, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner uee489ob5dcspgijmjhh9larkknfkab1.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "uee489ob5dcspgijmjhh9larkknfkab1" equal the hashed NSEC3-owner "uee489ob5dcspgijmjhh9larkknfkab1" and the hashed NextOwner "7nbfsioio9lampj987tk4mgengff5omg". 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, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner uee489ob5dcspgijmjhh9larkknfkab1.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.qleroy.xyz) sends a valid NSEC3 RR as result with the hashed owner name "eg61s5io6bohepn9r9jrhti612tta3v5" (unhashed: _tcp.qleroy.xyz). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner eg61s5io6bohepn9r9jrhti612tta3v5.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "2p4im3cgrb0g410gth6fgk5a83fasi00" (unhashed: *._tcp.qleroy.xyz) with the owner "uee489ob5dcspgijmjhh9larkknfkab1" and the NextOwner "7nbfsioio9lampj987tk4mgengff5omg". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner uee489ob5dcspgijmjhh9larkknfkab1.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query (_443._tcp.qleroy.xyz) sends a valid NSEC3 RR as result with the hashed query name "aac5auv72ai5vntsbeng4h6lf3o2no2r" between the hashed NSEC3-owner "7nbfsioio9lampj987tk4mgengff5omg" and the hashed NextOwner "dp05uul85afej9t25cc3sg8lar0jkrvt". So the zone confirmes the not-existence of that TLSA RR. Bitmap: A, RRSIG Validated: RRSIG-Owner 7nbfsioio9lampj987tk4mgengff5omg.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "uee489ob5dcspgijmjhh9larkknfkab1" equal the hashed NSEC3-owner "uee489ob5dcspgijmjhh9larkknfkab1" and the hashed NextOwner "7nbfsioio9lampj987tk4mgengff5omg". 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, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner uee489ob5dcspgijmjhh9larkknfkab1.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NoData-Proof required and found.

Zone: www.qleroy.xyz
www.qleroy.xyz	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 "dp05uul85afej9t25cc3sg8lar0jkrvt" between the hashed NSEC3-owner "dp05uul85afej9t25cc3sg8lar0jkrvt" and the hashed NextOwner "eg61s5io6bohepn9r9jrhti612tta3v5". So the parent zone confirmes the not-existence of a DS RR. Bitmap: TXT, RRSIG Validated: RRSIG-Owner dp05uul85afej9t25cc3sg8lar0jkrvt.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	RRSIG Type 16 validates the TXT - Result: 3\|welcome Validated: RRSIG-Owner www.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	A-Query sends a valid NSEC3 RR as result with the hashed query name "dp05uul85afej9t25cc3sg8lar0jkrvt" equal the hashed NSEC3-owner "dp05uul85afej9t25cc3sg8lar0jkrvt" and the hashed NextOwner "eg61s5io6bohepn9r9jrhti612tta3v5". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: TXT, RRSIG Validated: RRSIG-Owner dp05uul85afej9t25cc3sg8lar0jkrvt.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "dp05uul85afej9t25cc3sg8lar0jkrvt" equal the hashed NSEC3-owner "dp05uul85afej9t25cc3sg8lar0jkrvt" and the hashed NextOwner "eg61s5io6bohepn9r9jrhti612tta3v5". 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: TXT, RRSIG Validated: RRSIG-Owner dp05uul85afej9t25cc3sg8lar0jkrvt.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "dp05uul85afej9t25cc3sg8lar0jkrvt" equal the hashed NSEC3-owner "dp05uul85afej9t25cc3sg8lar0jkrvt" and the hashed NextOwner "eg61s5io6bohepn9r9jrhti612tta3v5". 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: TXT, RRSIG Validated: RRSIG-Owner dp05uul85afej9t25cc3sg8lar0jkrvt.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.qleroy.xyz) sends a valid NSEC3 RR as result with the hashed owner name "dp05uul85afej9t25cc3sg8lar0jkrvt" (unhashed: www.qleroy.xyz). So that's the Closest Encloser of the query name. Bitmap: TXT, RRSIG Validated: RRSIG-Owner dp05uul85afej9t25cc3sg8lar0jkrvt.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "hogituen5qkjmpbc7qgrm0jglbnvpjqp" (unhashed: _tcp.www.qleroy.xyz) with the owner "hbec0a7h8k042npl50v75pr39tihla22" and the NextOwner "i1t1v7g0uo4ct9o17bucctmb53dfq5sr". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: CNAME, RRSIG Validated: RRSIG-Owner hbec0a7h8k042npl50v75pr39tihla22.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "olpmamdu6avj0nqlc280n0kkalbhl40c" (unhashed: *.www.qleroy.xyz) with the owner "m7c1o6g6q3g0q4um4slf19jmnfuilkmq" and the NextOwner "orka5023q3m6hemq0trk8lqrfcuc9b24". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: A, RRSIG Validated: RRSIG-Owner m7c1o6g6q3g0q4um4slf19jmnfuilkmq.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "dp05uul85afej9t25cc3sg8lar0jkrvt" equal the hashed NSEC3-owner "dp05uul85afej9t25cc3sg8lar0jkrvt" and the hashed NextOwner "eg61s5io6bohepn9r9jrhti612tta3v5". 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: TXT, RRSIG Validated: RRSIG-Owner dp05uul85afej9t25cc3sg8lar0jkrvt.qleroy.xyz., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 17.04.2023, 16:46:00 +, Signature-Inception: 18.03.2023, 16:46:00 +, KeyTag 39003, Signer-Name: qleroy.xyz


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.qleroy.xyz	• dns12.ovh.net		•
qleroy.xyz	• dns12.ovh.net	213.251.188.131 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	X	2001:41d0:1:4a83::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS
	• ns12.ovh.net	213.251.128.131 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:1983::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
xyz	• generationxyz.nic.xyz / PDUS-VJ5JVS-CTI2KM		•
	• ns0.centralnic.net
	• x.nic.xyz / SFQY-BG7AF9-XTW0MS		•
	• y.nic.xyz / PDUS-VJ5JVS-CTI2KM		•
	• z.nic.xyz / SFQY-BG7AF9-XTW0MS		•

4. SOA-Entries

Domain:	xyz
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

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

Domain:	qleroy.xyz
Zone-Name:	qleroy.xyz
Primary:	dns12.ovh.net
Mail:	tech.ovh.net
Serial:	2023031801
Refresh:	86400
Retry:	3600
Expire:	3600000
TTL:	60
num Entries:	4

Domain:	www.qleroy.xyz
Zone-Name:	qleroy.xyz
Primary:	dns12.ovh.net
Mail:	tech.ovh.net
Serial:	2023031801
Refresh:	86400
Retry:	3600
Expire:	3600000
TTL:	60
num Entries:	1

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://qleroy.xyz/ 162.19.74.199	301	https://qleroy.xyz/ Html is minified: 109.03 %	0.056	A
Server: nginx/1.22.1
Date: Sat, 18 Mar 2023 17:50:10 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://qleroy.xyz/

• https://qleroy.xyz/ 162.19.74.199	-2		1.080	V
ConnectFailure - Unable to connect to the remote server

• http://qleroy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 162.19.74.199 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://qleroy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 109.03 %	0.057	A
Visible Content: 301 Moved Permanently nginx/1.22.1
Server: nginx/1.22.1
Date: Sat, 18 Mar 2023 17:50:11 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://qleroy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://qleroy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	-2		2.133	V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• https://162.19.74.199/ 162.19.74.199	-2		1.073	V
ConnectFailure - Unable to connect to the remote server

7. Comments

	1. General Results, most used to calculate the result
A	name "qleroy.xyz" is domain, public suffix is ".xyz", top-level-domain is ".xyz", top-level-domain-type is "generic", tld-manager is "XYZ.COM LLC", num .xyz-domains preloaded: 1564 (complete: 220007)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: qleroy.xyz 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: qleroy.xyz has no ipv6 address.
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.
C	Error - no version with Http-Status 200
H	Fatal error: No https - result with http-status 200, no encryption
V	https://qleroy.xyz/ 162.19.74.199	-2	Connect failure - perhaps firewall
V	https://qleroy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	-2	Connect failure - perhaps firewall
V	https://162.19.74.199/ 162.19.74.199	-2	Connect failure - perhaps firewall
X	Fatal error: Nameserver doesn't support TCP connection: dns12.ovh.net / 2001:41d0:1:4a83::1: Fatal error (-14). Details: Unable to read data from the transport connection: 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. - 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
X	Fatal error: Nameserver isn't defined or has 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 qleroy.xyz, 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.qleroy.xyz
	2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 11 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 11 Queries complete, 11 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.dns12.ovh.net (2001:41d0:1:4a83::1, 213.251.188.131), ns12.ovh.net (2001:41d0:1:1983::1)
	Ok (4 - 8):: An average of 5.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: dns12.ovh.net, ns12.ovh.net, 2 Name Servers included in Delegation: dns12.ovh.net, ns12.ovh.net, 2 Name Servers included in 1 Zone definitions: dns12.ovh.net, ns12.ovh.net, 1 Name Servers listed in SOA.Primary: dns12.ovh.net.
A	Good: Only one SOA.Primary Name Server found.: dns12.ovh.net.
A	Good: SOA.Primary Name Server included in the delegation set.: dns12.ovh.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: dns12.ovh.net, ns12.ovh.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: 2 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
	Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: net
	Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: ovh.net
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR
A	Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 213., 1 different subnets (first two Bytes): 213.251., 2 different subnets (first three Bytes): 213.251.128., 213.251.188.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:41d0:, 1 different subnets (first three blocks): 2001:41d0:0001:, 2 different subnets (first four blocks): 2001:41d0:0001:1983:, 2001:41d0:0001:4a83:
A	Good: Name Server IPv6 addresses from different subnets found.
X	Nameserver Timeout checking Echo Capitalization: dns12.ovh.net / 2001:41d0:1:4a83::1
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
A	Good: 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: ns0.centralnic.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
A	Good: All SOA have the same Serial Number
	Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
	4. Content- and Performance-critical Checks
	https://qleroy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	-2	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.
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: 74390 milliseconds, 74.390 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	2	2

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
4963971409 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-03-18 16:06:05	2023-06-16 16:06:04	qleroy.xyz - 1 entries
4933443404 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-03-11 19:36:40	2023-06-09 19:36:39	www.qleroy.xyz - 1 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	1	7

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
8901706327 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-03-11 18:36:40	2023-06-09 17:36:39	www.qleroy.xyz 1 entries
8199985415 leaf cert	CN=R3, O=Let's Encrypt, C=US	2022-12-12 20:03:30	2023-03-12 20:03:29	qleroy.xyz, www.qleroy.xyz 2 entries
7611790082 leaf cert	CN=R3, O=Let's Encrypt, C=US	2022-09-23 19:00:02	2022-12-22 20:00:01	qleroy.xyz, www.qleroy.xyz 2 entries
7070645257 leaf cert	CN=R3, O=Let's Encrypt, C=US	2022-07-05 18:50:11	2022-10-03 18:50:10	qleroy.xyz, www.qleroy.xyz 2 entries
6556516230 leaf cert	CN=R3, O=Let's Encrypt, C=US	2022-04-16 18:34:18	2022-07-15 18:34:17	qleroy.xyz, www.qleroy.xyz 2 entries
6055983921 leaf cert	CN=R3, O=Let's Encrypt, C=US	2022-01-26 19:17:26	2022-04-26 18:17:25	qleroy.xyz, www.qleroy.xyz 2 entries
5562832637 leaf cert	CN=R3, O=Let's Encrypt, C=US	2021-11-07 19:05:31	2022-02-05 19:05:30	qleroy.xyz, www.qleroy.xyz 2 entries

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: dns12.ovh.net, ns12.ovh.net

QNr.	Domain	Type	NS used
1	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
2	dns12.ovh.net: 2001:41d0:1:4a83::1, 213.251.188.131	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: dns10.ovh.net 2001:41d0:1:4a81::1, 213.251.188.129
	Answer: dns11.ovh.net 2001:41d0:1:4a82::1, 213.251.188.130
	Answer: dns15.ovh.net 2001:41d0:1:4a86::1, 213.251.188.134
	Answer: ns10.ovh.net 2001:41d0:1:1981::1, 213.251.128.129
	Answer: ns11.ovh.net 2001:41d0:1:1982::1, 213.251.128.130
	Answer: ns12.ovh.net 2001:41d0:1:1983::1
3	dns13.ovh.net	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net
	Answer: dns10.ovh.net 2001:41d0:1:4a81::1, 213.251.188.129
	Answer: dns11.ovh.net 2001:41d0:1:4a82::1, 213.251.188.130
	Answer: dns12.ovh.net 2001:41d0:1:4a83::1, 213.251.188.131
	Answer: dns15.ovh.net 2001:41d0:1:4a86::1, 213.251.188.134
	Answer: ns10.ovh.net 2001:41d0:1:1981::1, 213.251.128.129
	Answer: ns11.ovh.net 2001:41d0:1:1982::1, 213.251.128.130
	Answer: ns12.ovh.net 2001:41d0:1:1983::1
4	ns13.ovh.net	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net
	Answer: dns10.ovh.net 2001:41d0:1:4a81::1, 213.251.188.129
	Answer: dns11.ovh.net 2001:41d0:1:4a82::1, 213.251.188.130
	Answer: dns12.ovh.net 2001:41d0:1:4a83::1, 213.251.188.131
	Answer: dns15.ovh.net 2001:41d0:1:4a86::1, 213.251.188.134
	Answer: ns10.ovh.net 2001:41d0:1:1981::1, 213.251.128.129
	Answer: ns11.ovh.net 2001:41d0:1:1982::1, 213.251.128.130
	Answer: ns12.ovh.net 2001:41d0:1:1983::1
5	ns15.ovh.net	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net
	Answer: dns10.ovh.net 2001:41d0:1:4a81::1, 213.251.188.129
	Answer: dns11.ovh.net 2001:41d0:1:4a82::1, 213.251.188.130
	Answer: dns12.ovh.net 2001:41d0:1:4a83::1, 213.251.188.131
	Answer: dns15.ovh.net 2001:41d0:1:4a86::1, 213.251.188.134
	Answer: ns10.ovh.net 2001:41d0:1:1981::1, 213.251.128.129
	Answer: ns11.ovh.net 2001:41d0:1:1982::1, 213.251.128.130
	Answer: ns12.ovh.net 2001:41d0:1:1983::1
6	dns13.ovh.net: 213.251.188.132	A	dns10.ovh.net (2001:41d0:1:4a81::1)
7	dns13.ovh.net: 2001:41d0:1:4a84::1	AAAA	dns10.ovh.net (2001:41d0:1:4a81::1)
8	ns13.ovh.net: 213.251.128.132	A	dns10.ovh.net (2001:41d0:1:4a81::1)
9	ns13.ovh.net: 2001:41d0:1:1984::1	AAAA	dns10.ovh.net (2001:41d0:1:4a81::1)
10	ns15.ovh.net: 213.251.128.134	A	dns10.ovh.net (2001:41d0:1:4a81::1)
11	ns15.ovh.net: 2001:41d0:1:1986::1	AAAA	dns10.ovh.net (2001:41d0:1:4a81::1)

13. CAA - Entries

Domainname	Value	∑ Queries
www.qleroy.xyz	no CAA entry found	1
qleroy.xyz	no CAA entry found	1
xyz	no CAA entry found	1

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
qleroy.xyz	1\|www.qleroy.xyz	ok	1
qleroy.xyz	v=spf1 include:mx.ovh.com ~all	ok	1
www.qleroy.xyz	3\|welcome	ok	1
_acme-challenge.qleroy.xyz		Name Error - The domain name does not exist	1
_acme-challenge.www.qleroy.xyz		Name Error - The domain name does not exist	1
_acme-challenge.qleroy.xyz.qleroy.xyz		Name Error - The domain name does not exist	1
_acme-challenge.www.qleroy.xyz.qleroy.xyz		Name Error - The domain name does not exist	1
_acme-challenge.www.qleroy.xyz.www.qleroy.xyz		Name Error - The domain name does not exist	1

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

Type		Domain	Pref	Value	num Answers	Status
MX		qleroy.xyz	1	mx1.mail.ovh.net	3	ok
	A			188.165.36.237	1	ok
	CNAME				0	ok
MX		qleroy.xyz	5	mx2.mail.ovh.net	3	ok
	A			87.98.160.167	1	ok
	CNAME				0	ok
MX		qleroy.xyz	100	mx3.mail.ovh.net	3	ok
	A			91.121.53.175	1	ok
	CNAME				0	ok

16. Cipher Suites

No results

17. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=9ce89927-0498-4007-a159-90699d527673

Last Result: https://check-your-website.server-daten.de/?q=qleroy.xyz - 2023-03-18 18:49:21

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

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

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