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

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 11019, 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: 10.09.2023, 00:00:00 +, Signature-Inception: 20.08.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: ovh
ovh	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 24939, DigestType 2 and Digest AqP3ibfWxyZRPuut9/ZHQf7RrNV0BTOdnVAZHGIM2RQ=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner ovh., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.09.2023, 05:00:00 +, Signature-Inception: 21.08.2023, 04:00:00 +, KeyTag 11019, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 4883, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ovh., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2023, 08:04:58 +, Signature-Inception: 29.07.2023, 05:47:54 +, KeyTag 24939, Signer-Name: ovh


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


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

Zone: mydomoticz.ovh
mydomoticz.ovh	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 "3qd67d5rbj7t1dnsprjs0irk0bl7uljo" between the hashed NSEC3-owner "3qa5qf5irqesf9nj06dohjvr3el9dvua" and the hashed NextOwner "3qeqhpisabl8su4btncodib5spka0agq". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 3qa5qf5irqesf9nj06dohjvr3el9dvua.ovh., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 17.10.2023, 02:42:06 +, Signature-Inception: 18.08.2023, 02:35:32 +, KeyTag 4883, Signer-Name: ovh


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "hq4qgmr0hm4evu0oo4vckgpoqv1muhmv" as Owner. That's the Hash of "ovh" with the NextHashedOwnerName "hq4rrgpi2vu50761bke3t0vlbff1jbhh". So that domain name is the Closest Encloser of "mydomoticz.ovh". Opt-Out: True. Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner hq4qgmr0hm4evu0oo4vckgpoqv1muhmv.ovh., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 08.10.2023, 01:07:31 +, Signature-Inception: 09.08.2023, 00:27:13 +, KeyTag 4883, Signer-Name: ovh


	The ClosestEncloser says, that "*.ovh" with the Hash "tn8gtfabgjo0288i7k2tpk340asq29cv" 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 "tn8a2a59hfpgj77lvcr26a77e6o9k8qp" and the Next Owner "tn91irvjoim6q6h3vcdibtrugog40ijb", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner tn8a2a59hfpgj77lvcr26a77e6o9k8qp.ovh., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 27.09.2023, 04:11:14 +, Signature-Inception: 24.07.2023, 10:18:21 +, KeyTag 4883, Signer-Name: ovh

Zone: www.mydomoticz.ovh
www.mydomoticz.ovh	0 DS RR in the parent zone found


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "hq4qgmr0hm4evu0oo4vckgpoqv1muhmv" as Owner. That's the Hash of "ovh" with the NextHashedOwnerName "hq4rrgpi2vu50761bke3t0vlbff1jbhh". So that domain name is the Closest Encloser of "www.mydomoticz.ovh". Opt-Out: True. Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner hq4qgmr0hm4evu0oo4vckgpoqv1muhmv.ovh., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 08.10.2023, 01:07:31 +, Signature-Inception: 09.08.2023, 00:27:13 +, KeyTag 4883, Signer-Name: ovh


	The ClosestEncloser says, that "*.ovh" with the Hash "tn8gtfabgjo0288i7k2tpk340asq29cv" 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 "tn8a2a59hfpgj77lvcr26a77e6o9k8qp" and the Next Owner "tn91irvjoim6q6h3vcdibtrugog40ijb", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner tn8a2a59hfpgj77lvcr26a77e6o9k8qp.ovh., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 27.09.2023, 04:11:14 +, Signature-Inception: 24.07.2023, 10:18:21 +, KeyTag 4883, Signer-Name: ovh

3. Name Servers

Domain	Nameserver
www.mydomoticz.ovh	• a.nic.fr
mydomoticz.ovh	• a.nic.fr
ovh	• a.nic.fr
	• d.nic.fr / dns.ams.nic.fr	•
	• f.ext.nic.fr / s2.cmx	•
	• g.ext.nic.fr / 1.ber.pch	•

4. SOA-Entries

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

Domain:	ovh
Zone-Name:	ovh
Primary:	a.nic.fr
Mail:	dnsmaster.afnic.fr
Serial:	2223400226
Refresh:	3600
Retry:	1800
Expire:	3600000
TTL:	600
num Entries:	3

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

Domain:	www.mydomoticz.ovh
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "mydomoticz.ovh" is domain, public suffix is ".ovh", top-level-domain is ".ovh", top-level-domain-type is "generic", tld-manager is "OVH SAS", num .ovh-domains preloaded: 208 (complete: 231048)
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
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.mydomoticz.ovh
	2. Header-Checks
U		No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A
A
A	Info:: 4 different Name Servers found: a.nic.fr, d.nic.fr, f.ext.nic.fr, g.ext.nic.fr, 3 Name Servers included in Delegation: d.nic.fr, f.ext.nic.fr, g.ext.nic.fr, 3 Name Servers included in 2 Zone definitions: d.nic.fr, f.ext.nic.fr, g.ext.nic.fr, 1 Name Servers listed in SOA.Primary: a.nic.fr.
A	Good: Only one SOA.Primary Name Server found.: a.nic.fr.
	Error: SOA.Primary Name Server not included in the delegation set.: a.nic.fr.
A	Good: All Name Server Domain Names have a Public Suffix.
A
A	Good: Nameserver supports TCP connections: 3 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 3 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: a.nic.fr: 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: a.nic.fr: 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: a.nic.fr: 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: d.nic.fr: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns.ams.nic.fr). 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
	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
	Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 13903 milliseconds, 13.903 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)

No CertSpotter - CT-Log entries found

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

No CRT - CT-Log entries found

11. Html-Content - Entries

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

12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address - Informations found

13. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
ovh	0		no CAA entry found	1	0

14. TXT - Entries

No TXT entries found

15. DomainService - Entries

No DomainServiceEntries entries found

16. Cipher Suites

No Ciphers found

17. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=ba2c5249-7526-4886-b259-d0a3073c38a5

Last Result: https://check-your-website.server-daten.de/?q=mydomoticz.ovh - 2023-08-21 20:54:07

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

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

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