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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
29.11.2024 16:53:21

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
hubble-ui.infra.tehtris.dev	A	141.95.245.199 Paris/Île-de-France/France (FR) - OVH SAS Hostname: ip199.ip-141-95-245.eu	yes	1	0
	AAAA		yes
www.hubble-ui.infra.tehtris.dev	A	141.95.245.199 Paris/Île-de-France/France (FR) - OVH SAS Hostname: ip199.ip-141-95-245.eu	yes	1	0
	AAAA		yes
*.infra.tehtris.dev	A	141.95.245.199	yes
	AAAA		yes
	CNAME		yes
*.hubble-ui.infra.tehtris.dev	A	141.95.245.199	yes
	AAAA		yes
	CNAME		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 61050, 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.2024, 00:00:00 +, Signature-Inception: 20.11.2024, 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: dev
dev	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 60074, DigestType 2 and Digest uULizlrr9i/KWdBXB+bbt5UhHVQNitugLp6J6DNCR4U=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2024, 05:00:00 +, Signature-Inception: 29.11.2024, 04:00:00 +, KeyTag 61050, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 7030, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 19.12.2024, 20:52:41 +, Signature-Inception: 27.11.2024, 20:52:41 +, KeyTag 60074, Signer-Name: dev


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


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

Zone: tehtris.dev
tehtris.dev	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 42367, DigestType 2 and Digest +YK8G/p7kfgNNMX+uXLuxfyoujKdy8qGjP7TxueY7os=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner tehtris.dev., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 19.12.2024, 20:52:41 +, Signature-Inception: 27.11.2024, 20:52:41 +, KeyTag 7030, Signer-Name: dev


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 32733, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner tehtris.dev., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	RRSIG-Owner tehtris.dev., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 42367, Signer-Name: tehtris.dev


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


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


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

Zone: infra.tehtris.dev
infra.tehtris.dev	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 "tehevpgngulamlbsg50q8t3do3jvocqo" between the hashed NSEC3-owner "tehevpgngulamlbsg50q8t3do3jvocqo" and the hashed NextOwner "v18n0n9crrdpjpf6kqusv5ahdj4j5bal". So the parent zone confirmes the not-existence of a DS RR. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	0 DNSKEY RR found




Zone: hubble-ui.infra.tehtris.dev
hubble-ui.infra.tehtris.dev	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 "8cl14knfbp23il8g54o99p3af6l99jko" between the hashed NSEC3-owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the hashed NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tehevpgngulamlbsg50q8t3do3jvocqo" as Owner. That's the Hash of "infra.tehtris.dev" with the NextHashedOwnerName "v18n0n9crrdpjpf6kqusv5ahdj4j5bal". So that domain name is the Closest Encloser of "hubble-ui.infra.tehtris.dev". Opt-Out: False. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	The ClosestEncloser says, that "*.infra.tehtris.dev" with the Hash "o1nulgrcvq7f2r75bbjutanocog52iq3" 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 "o1nulgrcvq7f2r75bbjutanocog52iq3" and the Next Owner "p4kgsie5nvc7gtptlfhhq64m0n0utnid", 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, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 141.95.245.199. 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 hubble-ui.infra.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "8cl14knfbp23il8g54o99p3af6l99jko". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "8cl14knfbp23il8g54o99p3af6l99jko". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "8cl14knfbp23il8g54o99p3af6l99jko". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.hubble-ui.infra.tehtris.dev) sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "8cl14knfbp23il8g54o99p3af6l99jko" (unhashed: hubble-ui.infra.tehtris.dev) with the owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "qmnhso81os44hjef2fu6eiaji291sn1d". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "8cl14knfbp23il8g54o99p3af6l99jko". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	A-Query sends a valid NSEC3 RR as result with the hashed query name "8cl14knfbp23il8g54o99p3af6l99jko" between the hashed NSEC3-owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the hashed NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So the zone confirmes the not-existence of that A RR. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: Validated Data sent, but the NSEC3Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "8cl14knfbp23il8g54o99p3af6l99jko" between the hashed NSEC3-owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the hashed NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So the zone confirmes the not-existence of that CNAME RR. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "8cl14knfbp23il8g54o99p3af6l99jko" between the hashed NSEC3-owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the hashed NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So the zone confirmes the not-existence of that TXT RR. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "8cl14knfbp23il8g54o99p3af6l99jko" between the hashed NSEC3-owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the hashed NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So the zone confirmes the not-existence of that AAAA RR. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "8cl14knfbp23il8g54o99p3af6l99jko" between the hashed NSEC3-owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the hashed NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So the zone confirmes the not-existence of that CAA RR. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.

Zone: www.hubble-ui.infra.tehtris.dev
www.hubble-ui.infra.tehtris.dev	0 DS RR in the parent zone found


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tehevpgngulamlbsg50q8t3do3jvocqo" as Owner. That's the Hash of "infra.tehtris.dev" with the NextHashedOwnerName "v18n0n9crrdpjpf6kqusv5ahdj4j5bal". So that domain name is the Closest Encloser of "www.hubble-ui.infra.tehtris.dev". Opt-Out: False. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	The ClosestEncloser says, that "*.infra.tehtris.dev" with the Hash "o1nulgrcvq7f2r75bbjutanocog52iq3" 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 "o1nulgrcvq7f2r75bbjutanocog52iq3" and the Next Owner "p4kgsie5nvc7gtptlfhhq64m0n0utnid", 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, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	RRSIG Type 1 validates the A - Result: 141.95.245.199. 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 www.hubble-ui.infra.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	A-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "8cl14knfbp23il8g54o99p3af6l99jko" (unhashed: hubble-ui.infra.tehtris.dev) with the owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "8cl14knfbp23il8g54o99p3af6l99jko" (unhashed: hubble-ui.infra.tehtris.dev) with the owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "35vb46e53d36m7ag4lqp9voo0hcakm96". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "8cl14knfbp23il8g54o99p3af6l99jko" (unhashed: hubble-ui.infra.tehtris.dev) with the owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "35vb46e53d36m7ag4lqp9voo0hcakm96". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "8cl14knfbp23il8g54o99p3af6l99jko" (unhashed: hubble-ui.infra.tehtris.dev) with the owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "35vb46e53d36m7ag4lqp9voo0hcakm96". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.hubble-ui.infra.tehtris.dev) sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "8cl14knfbp23il8g54o99p3af6l99jko" (unhashed: hubble-ui.infra.tehtris.dev) with the owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.www.hubble-ui.infra.tehtris.dev) sends a valid NSEC3 RR as result with the hashed query name "8oe36arfk2rov3oa0iigds4j0t3gthiq" between the hashed NSEC3-owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the hashed NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So the zone confirmes the not-existence of that TLSA RR. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "8oe36arfk2rov3oa0iigds4j0t3gthiq". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "tehevpgngulamlbsg50q8t3do3jvocqo" (unhashed: infra.tehtris.dev). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner tehevpgngulamlbsg50q8t3do3jvocqo.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "8cl14knfbp23il8g54o99p3af6l99jko" (unhashed: hubble-ui.infra.tehtris.dev) with the owner "7qam9md58ti4dqcdn3v59v4if8teji6q" and the NextOwner "962si3gq6lui6f7ipvsmbp45bfpp2pkk". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 7qam9md58ti4dqcdn3v59v4if8teji6q.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "o1nulgrcvq7f2r75bbjutanocog52iq3" (unhashed: *.infra.tehtris.dev) as the Wildcard-Expansion of the Closest Encloser of the query name "35vb46e53d36m7ag4lqp9voo0hcakm96". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner o1nulgrcvq7f2r75bbjutanocog52iq3.tehtris.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 25.12.2024, 18:37:21 +, Signature-Inception: 25.11.2024, 18:37:21 +, KeyTag 32733, Signer-Name: tehtris.dev


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.hubble-ui.infra.tehtris.dev	• dns104.ovh.net		•
hubble-ui.infra.tehtris.dev	• dns104.ovh.net	213.251.188.148 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:4a94::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
infra.tehtris.dev	• dns104.ovh.net	213.251.188.148 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:4a94::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
tehtris.dev	• dns104.ovh.net	213.251.188.148 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:4a94::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	• ns104.ovh.net	213.251.128.148 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:1994::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
dev	• ns-tld1.charlestonroadregistry.com		•
	• ns-tld2.charlestonroadregistry.com		•
	• ns-tld3.charlestonroadregistry.com		•
	• ns-tld4.charlestonroadregistry.com		•
	• ns-tld5.charlestonroadregistry.com		•

4. SOA-Entries

Domain:	dev
Zone-Name:	dev
Primary:	ns-tld1.charlestonroadregistry.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	1
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	5

Domain:	tehtris.dev
Zone-Name:	tehtris.dev
Primary:	dns104.ovh.net
Mail:	tech.ovh.net
Serial:	2024112500
Refresh:	86400
Retry:	3600
Expire:	3600000
TTL:	60
num Entries:	4

Domain:	infra.tehtris.dev
Zone-Name:	tehtris.dev
Primary:	dns104.ovh.net
Mail:	tech.ovh.net
Serial:	2024112500
Refresh:	86400
Retry:	3600
Expire:	3600000
TTL:	60
num Entries:	2

Domain:	hubble-ui.infra.tehtris.dev
Zone-Name:	tehtris.dev
Primary:	dns104.ovh.net
Mail:	tech.ovh.net
Serial:	2024112500
Refresh:	86400
Retry:	3600
Expire:	3600000
TTL:	60
num Entries:	2

Domain:	www.hubble-ui.infra.tehtris.dev
Zone-Name:	tehtris.dev
Primary:	dns104.ovh.net
Mail:	tech.ovh.net
Serial:	2024112500
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

Domainname	Http-Status	Sec.	G
• http://hubble-ui.infra.tehtris.dev/ 141.95.245.199	-14	10.010	T
Timeout - The operation has timed out.

• http://www.hubble-ui.infra.tehtris.dev/ 141.95.245.199	-14	10.010	T
Timeout - The operation has timed out.

• https://hubble-ui.infra.tehtris.dev/ 141.95.245.199	-14	10.010	T
Timeout - The operation has timed out.

• https://www.hubble-ui.infra.tehtris.dev/ 141.95.245.199	-14	10.013	T
Timeout - The operation has timed out.

• http://hubble-ui.infra.tehtris.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 141.95.245.199	-14	10.013	T
Timeout - The operation has timed out.
Visible Content:

• http://www.hubble-ui.infra.tehtris.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 141.95.245.199	-14	10.017	T
Timeout - The operation has timed out.
Visible Content:

• https://141.95.245.199/ 141.95.245.199	-14	10.006	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "hubble-ui.infra.tehtris.dev" is subdomain, public suffix is ".dev", top-level-domain is ".dev", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .dev-domains preloaded: 15 (complete: 263653)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: hubble-ui.infra.tehtris.dev has only one ip address.
	Warning: Only one ip address found: www.hubble-ui.infra.tehtris.dev 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: hubble-ui.infra.tehtris.dev 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.hubble-ui.infra.tehtris.dev has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	Excellent: Main Domain is in the Google-Preload-List
A	Excellent: Main Domain is in the Mozilla/Firefox-Preload-List
A	HSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
	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 hubble-ui.infra.tehtris.dev, 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.hubble-ui.infra.tehtris.dev, 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.hubble-ui.infra.tehtris.dev
	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:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: dns104.ovh.net, ns104.ovh.net, 2 Name Servers included in Delegation: dns104.ovh.net, ns104.ovh.net, 2 Name Servers included in 1 Zone definitions: dns104.ovh.net, ns104.ovh.net, 1 Name Servers listed in SOA.Primary: dns104.ovh.net.
A	Good: Only one SOA.Primary Name Server found.: dns104.ovh.net.
A	Good: SOA.Primary Name Server included in the delegation set.: dns104.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: dns104.ovh.net, ns104.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:1994:, 2001:41d0:0001:4a94:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 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
	http://hubble-ui.infra.tehtris.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 141.95.245.199	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.hubble-ui.infra.tehtris.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 141.95.245.199	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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: 152693 milliseconds, 152.693 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. 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.

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns104.ovh.net, ns104.ovh.net

QNr.	Domain	Type	NS used
1	net	NS	k.root-servers.net (2001:7fd::1)
	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	dns104.ovh.net	NS	a.gtld-servers.net (2001:503:a83e::2: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: dns13.ovh.net 2001:41d0:1:4a84::1, 213.251.188.132
	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, 213.251.128.131
	Answer: ns13.ovh.net 2001:41d0:1:1984::1, 213.251.128.132
	Answer: ns15.ovh.net 2001:41d0:1:1986::1, 213.251.128.134
3	ns104.ovh.net	NS	a.gtld-servers.net (2001:503:a83e::2: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: dns13.ovh.net 2001:41d0:1:4a84::1, 213.251.188.132
	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, 213.251.128.131
	Answer: ns13.ovh.net 2001:41d0:1:1984::1, 213.251.128.132
	Answer: ns15.ovh.net 2001:41d0:1:1986::1, 213.251.128.134
4	dns104.ovh.net: 213.251.188.148	A	dns10.ovh.net (2001:41d0:1:4a81::1)
5	dns104.ovh.net: 2001:41d0:1:4a94::1	AAAA	dns10.ovh.net (2001:41d0:1:4a81::1)
6	ns104.ovh.net: 213.251.128.148	A	dns10.ovh.net (2001:41d0:1:4a81::1)
7	ns104.ovh.net: 2001:41d0:1:1994::1	AAAA	dns10.ovh.net (2001:41d0:1:4a81::1)

14. CAA - Entries

Domainname	Value	∑ Queries
www.hubble-ui.infra.tehtris.dev	no CAA entry found	1
hubble-ui.infra.tehtris.dev	no CAA entry found	1
infra.tehtris.dev	no CAA entry found	1
tehtris.dev	no CAA entry found	1
dev	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
infra.tehtris.dev	ok	1
hubble-ui.infra.tehtris.dev	ok	1
www.hubble-ui.infra.tehtris.dev	ok	1
_acme-challenge.hubble-ui.infra.tehtris.dev	missing entry or wrong length	1
_acme-challenge.www.hubble-ui.infra.tehtris.dev	missing entry or wrong length	1
_acme-challenge.hubble-ui.infra.tehtris.dev.infra.tehtris.dev	perhaps wrong	1
_acme-challenge.hubble-ui.infra.tehtris.dev.hubble-ui.infra.tehtris.dev	perhaps wrong	1
_acme-challenge.www.hubble-ui.infra.tehtris.dev.hubble-ui.infra.tehtris.dev	perhaps wrong	1
_acme-challenge.www.hubble-ui.infra.tehtris.dev.www.hubble-ui.infra.tehtris.dev	perhaps wrong	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=ba603eb5-2408-4784-907c-8039b5fa0491

Last Result: https://check-your-website.server-daten.de/?q=hubble-ui.infra.tehtris.dev - 2024-12-02 15:37:01

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

<a href="https://check-your-website.server-daten.de/?q=hubble-ui.infra.tehtris.dev" target="_blank">Check this Site: hubble-ui.infra.tehtris.dev</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=hubble-ui.infra.tehtris.dev