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

...

skip EDNS-Check

skip Content-Check

check links

Server error

Checked:
05.07.2025 20:01:32

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
pct-front-int.datasense-group.fr	CNAME	dev.datasense-group.fr	yes	1	0
	A	192.99.32.127 Beauharnois/Quebec/Canada (CA) - OVH SAS Hostname: ns503622.ip-192-99-32.net	yes
www.pct-front-int.datasense-group.fr		Name Error	yes	1	0
*.datasense-group.fr	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.pct-front-int.datasense-group.fr	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


	4 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 46441, Flags 256


	Public Key with Algorithm 8, KeyTag 53148, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 13, KeyTag 29133, DigestType 2 and Digest EwPo2o+2DbUA1b6h7l3JorzJPf4vxD00ZXZlj+zPV0k=


	2 RRSIG RR to validate DS RR found


	RRSIG-Owner fr., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.07.2025, 17:00:00 +, Signature-Inception: 05.07.2025, 16:00:00 +, KeyTag 46441, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 52627, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner fr., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 20.07.2025, 05:07:22 +, Signature-Inception: 20.06.2025, 04:32:29 +, KeyTag 29133, Signer-Name: fr


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


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

Zone: datasense-group.fr
datasense-group.fr	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 50620, DigestType 2 and Digest JaxuSsKxuUgPSDP14TlCxk121jtti182mW0v8Gv4tBw=


	2 RRSIG RR to validate DS RR found


	RRSIG-Owner datasense-group.fr., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.08.2025, 07:03:53 +, Signature-Inception: 03.07.2025, 06:13:21 +, KeyTag 52627, Signer-Name: fr


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 25933, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner datasense-group.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	RRSIG-Owner datasense-group.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 50620, Signer-Name: datasense-group.fr


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


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


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

Zone: pct-front-int.datasense-group.fr
pct-front-int.datasense-group.fr	0 DS RR in the parent zone found


	RRSIG Type 5 validates the CNAME - Result: dev.datasense-group.fr Validated: RRSIG-Owner pct-front-int.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr

Zone: www.pct-front-int.datasense-group.fr
www.pct-front-int.datasense-group.fr	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 "fu3k518lqiems441m1bmcspej7j704ba" between the hashed NSEC3-owner "ekbsprn4126dirpbqq5cdegjbsus3b9b" and the hashed NextOwner "hgf6o43rktd3h09l18incv9se74shegh". So the parent zone confirmes the not-existence of a DS RR. Bitmap: CNAME, RRSIG Validated: RRSIG-Owner ekbsprn4126dirpbqq5cdegjbsus3b9b.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "5545ucnjik1u3ek3srap6qc5480kvl1l" as Owner. That's the Hash of "pct-front-int.datasense-group.fr" with the NextHashedOwnerName "76hps47tprmrr3tdjag3s4okct2fab2u". So that domain name is the Closest Encloser of "www.pct-front-int.datasense-group.fr". Opt-Out: False. Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 5545ucnjik1u3ek3srap6qc5480kvl1l.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	The ClosestEncloser says, that "*.pct-front-int.datasense-group.fr" with the Hash "llrh2g2jpc12f018sjohfb31rr3popg0" 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 "lfn0p3lh1sqeo3ts2m5b1053orqh0c1c" and the Next Owner "n4mqknvs0jav0ba6kafapmrve68et6ub", 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: CNAME, RRSIG Validated: RRSIG-Owner lfn0p3lh1sqeo3ts2m5b1053orqh0c1c.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	4 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 46441, Flags 256


	Public Key with Algorithm 8, KeyTag 53148, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 13, KeyTag 29133, DigestType 2 and Digest EwPo2o+2DbUA1b6h7l3JorzJPf4vxD00ZXZlj+zPV0k=


	2 RRSIG RR to validate DS RR found


	RRSIG-Owner fr., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.07.2025, 17:00:00 +, Signature-Inception: 05.07.2025, 16:00:00 +, KeyTag 46441, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 52627, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner fr., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 20.07.2025, 05:07:22 +, Signature-Inception: 20.06.2025, 04:32:29 +, KeyTag 29133, Signer-Name: fr


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


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

Zone: datasense-group.fr
datasense-group.fr	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 50620, DigestType 2 and Digest JaxuSsKxuUgPSDP14TlCxk121jtti182mW0v8Gv4tBw=


	2 RRSIG RR to validate DS RR found


	RRSIG-Owner datasense-group.fr., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.08.2025, 07:03:53 +, Signature-Inception: 03.07.2025, 06:13:21 +, KeyTag 52627, Signer-Name: fr


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 25933, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner datasense-group.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	RRSIG-Owner datasense-group.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 50620, Signer-Name: datasense-group.fr


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


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


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

Zone: dev.datasense-group.fr
dev.datasense-group.fr	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 "hgf6o43rktd3h09l18incv9se74shegh" between the hashed NSEC3-owner "hgf6o43rktd3h09l18incv9se74shegh" and the hashed NextOwner "j8tuevimacdm7l8al7fb5itu6uig0a5u". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, RRSIG Validated: RRSIG-Owner hgf6o43rktd3h09l18incv9se74shegh.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 192.99.32.127 Validated: RRSIG-Owner dev.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "hgf6o43rktd3h09l18incv9se74shegh" equal the hashed NSEC3-owner "hgf6o43rktd3h09l18incv9se74shegh" and the hashed NextOwner "j8tuevimacdm7l8al7fb5itu6uig0a5u". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner hgf6o43rktd3h09l18incv9se74shegh.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "hgf6o43rktd3h09l18incv9se74shegh" equal the hashed NSEC3-owner "hgf6o43rktd3h09l18incv9se74shegh" and the hashed NextOwner "j8tuevimacdm7l8al7fb5itu6uig0a5u". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner hgf6o43rktd3h09l18incv9se74shegh.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "hgf6o43rktd3h09l18incv9se74shegh" equal the hashed NSEC3-owner "hgf6o43rktd3h09l18incv9se74shegh" and the hashed NextOwner "j8tuevimacdm7l8al7fb5itu6uig0a5u". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner hgf6o43rktd3h09l18incv9se74shegh.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.dev.datasense-group.fr) sends a valid NSEC3 RR as result with the hashed owner name "hgf6o43rktd3h09l18incv9se74shegh" (unhashed: dev.datasense-group.fr). So that's the Closest Encloser of the query name. Bitmap: A, RRSIG Validated: RRSIG-Owner hgf6o43rktd3h09l18incv9se74shegh.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "rra5euo1gehdime9h47hvkkjjma6tbgt" (unhashed: _tcp.dev.datasense-group.fr) with the owner "p0f4guubgn6hm6eibaocpq714221p011" and the NextOwner "rrpivjoacla1qqsjul19l134ph2inm9b". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: CNAME, RRSIG Validated: RRSIG-Owner p0f4guubgn6hm6eibaocpq714221p011.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	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 "fk8frhrkkmjagtnf9nrq60hvlufm5nk2" (unhashed: *.dev.datasense-group.fr) with the owner "ekbsprn4126dirpbqq5cdegjbsus3b9b" and the NextOwner "hgf6o43rktd3h09l18incv9se74shegh". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: CNAME, RRSIG Validated: RRSIG-Owner ekbsprn4126dirpbqq5cdegjbsus3b9b.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "hgf6o43rktd3h09l18incv9se74shegh" equal the hashed NSEC3-owner "hgf6o43rktd3h09l18incv9se74shegh" and the hashed NextOwner "j8tuevimacdm7l8al7fb5itu6uig0a5u". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner hgf6o43rktd3h09l18incv9se74shegh.datasense-group.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 27.07.2025, 06:32:04 +, Signature-Inception: 27.06.2025, 06:32:04 +, KeyTag 25933, Signer-Name: datasense-group.fr


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.pct-front-int.datasense-group.fr	• dns101.ovh.net
datasense-group.fr	• dns101.ovh.net	213.251.188.145 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:4a91::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	• ns101.ovh.net	213.251.128.145 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:1991::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
fr	• a.nic.fr
	• d.nic.fr / dns.nyc.nic.fr		•
	• f.ext.nic.fr / s2.dex		•
	• g.ext.nic.fr / 4.fra.pch		•

dev.datasense-group.fr	• dns101.ovh.net	213.251.188.145 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:4a91::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
datasense-group.fr	• dns101.ovh.net	213.251.188.145 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:4a91::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	• ns101.ovh.net	213.251.128.145 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:1991::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
fr	• a.nic.fr
	• d.nic.fr / dns.nyc.nic.fr		•
	• f.ext.nic.fr / s2.dex		•
	• g.ext.nic.fr / 2.fra.pch		•

4. SOA-Entries

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

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

Domain:	datasense-group.fr
Zone-Name:	datasense-group.fr
Primary:	dns101.ovh.net
Mail:	tech.ovh.net
Serial:	2025062700
Refresh:	86400
Retry:	3600
Expire:	3600000
TTL:	300
num Entries:	4

Domain:	www.pct-front-int.datasense-group.fr
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1


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

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

Domain:	datasense-group.fr
Zone-Name:	datasense-group.fr
Primary:	dns101.ovh.net
Mail:	tech.ovh.net
Serial:	2025062700
Refresh:	86400
Retry:	3600
Expire:	3600000
TTL:	300
num Entries:	4

Domain:	dev.datasense-group.fr
Zone-Name:	datasense-group.fr
Primary:	dns101.ovh.net
Mail:	tech.ovh.net
Serial:	2025062700
Refresh:	86400
Retry:	3600
Expire:	3600000
TTL:	300
num Entries:	2

5. Screenshots

Startaddress: https://pct-front-int.datasense-group.fr/, address used: https://pct-front-int.datasense-group.fr/, Screenshot created 2025-07-05 20:04:22 +00:0 url is insecure, certificate invalid

Mobil (412px x 732px)

1055 milliseconds

Screenshot mobile - https://pct-front-int.datasense-group.fr/

Mobil + Landscape (732px x 412px)

1064 milliseconds

Screenshot mobile landscape - https://pct-front-int.datasense-group.fr/

Screen (1280px x 1680px)

1119 milliseconds

Screenshot Desktop - https://pct-front-int.datasense-group.fr/

Mobile- and other Chrome-Checks

	width	height
visual Viewport	412	732
content Size	412	732

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

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://pct-front-int.datasense-group.fr/ 192.99.32.127	308	https://pct-front-int.datasense-group.fr/ Html is minified: 109.33 %	0.216	A
Date: Sat, 05 Jul 2025 18:02:25 GMT
Connection: keep-alive
Location: https://pct-front-int.datasense-group.fr/
Content-Type: text/html
Content-Length: 164

• https://pct-front-int.datasense-group.fr/ 192.99.32.127	503	Html is minified: 107.95 %	4.484	N
Service Temporarily Unavailable
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Date: Sat, 05 Jul 2025 18:02:26 GMT
Connection: keep-alive
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Type: text/html
Content-Length: 190

• http://pct-front-int.datasense-group.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 192.99.32.127 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	308	https://pct-front-int.datasense-group.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 109.33 % Other inline scripts (∑/total): 0/0	0.117	A
Visible Content:
Date: Sat, 05 Jul 2025 18:02:31 GMT
Connection: keep-alive
Location: https://pct-front-int.datasense-group.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Type: text/html
Content-Length: 164

• https://pct-front-int.datasense-group.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	503	Html is minified: 107.95 % Other inline scripts (∑/total): 0/0	4.140	N
Service Temporarily Unavailable
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Visible Content:
Date: Sat, 05 Jul 2025 18:02:39 GMT
Connection: keep-alive
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Type: text/html
Content-Length: 190

• https://192.99.32.127/ 192.99.32.127 gzip used - 821 / 1412 - 41.86 % Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/96	200	Html is minified: 199.72 % Other inline scripts (∑/total): 0/0	4.567	N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Date: Sat, 05 Jul 2025 18:02:32 GMT
Connection: keep-alive
Accept-Ranges: bytes
Cache-Control: no-store, must-revalidate, no-cache
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Type: text/html; charset=utf-8
Content-Length: 821
Content-Encoding: gzip
Last-Modified: Fri, 16 Sep 2022 11:49:34 GMT

7. Comments

	1. General Results, most used to calculate the result
A	name "pct-front-int.datasense-group.fr" is subdomain, public suffix is ".fr", top-level-domain is ".fr", top-level-domain-type is "country-code", Country is France, tld-manager is "Association Française pour le Nommage Internet en Coopération (A.F.N.I.C.)", num .fr-domains preloaded: 3890 (complete: 271405)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: pct-front-int.datasense-group.fr 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: pct-front-int.datasense-group.fr has no ipv6 address.
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
A	Good: destination is https
A	Good: No cookie sent via http.
A	Good: every https has a Strict Transport Security Header
A	Good: HSTS has includeSubdomains - directive
	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)
A	http://pct-front-int.datasense-group.fr/ 192.99.32.127	308	https://pct-front-int.datasense-group.fr/	Correct redirect http - https with the same domain name
B	Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15724800 seconds = 182 days found
N	https://pct-front-int.datasense-group.fr/ 192.99.32.127	503		Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
N	https://pct-front-int.datasense-group.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	503		Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
N	https://192.99.32.127/ 192.99.32.127	200		Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
	Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain pct-front-int.datasense-group.fr, 1 ip addresses, 1 different http results.
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.pct-front-int.datasense-group.fr
	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	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: dns101.ovh.net, ns101.ovh.net, 2 Name Servers included in Delegation: dns101.ovh.net, ns101.ovh.net, 2 Name Servers included in 1 Zone definitions: dns101.ovh.net, ns101.ovh.net, 1 Name Servers listed in SOA.Primary: dns101.ovh.net.
A	Good: Only one SOA.Primary Name Server found.: dns101.ovh.net.
A	Good: SOA.Primary Name Server included in the delegation set.: dns101.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	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:1991:, 2001:41d0:0001:4a91:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 8 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 8 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 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: 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.nyc.nic.fr). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: d.nic.fr: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: ok (dns.nyc.nic.fr). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: dns101.ovh.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://pct-front-int.datasense-group.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	503		Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 500 - 599, Server Error. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	https://192.99.32.127/ 192.99.32.127	200		Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
	https://192.99.32.127/ 192.99.32.127	200		Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
A	Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
	https://192.99.32.127/ 192.99.32.127	200		Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 4 script elements without defer/async.
A	Good: All checked attribute values are enclosed in quotation marks (" or ').
A	Info: No img element found, no alt attribute checked
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 177246 milliseconds, 177.246 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

pct-front-int.datasense-group.fr

192.99.32.127

443

Certificate/chain invalid and wrong name

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

pct-front-int.datasense-group.fr

192.99.32.127

443

Certificate/chain invalid and wrong name

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Self signed certificate		1	CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co

pct-front-int.datasense-group.fr

443

Certificate/chain invalid and wrong name

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

pct-front-int.datasense-group.fr

443

Certificate/chain invalid and wrong name

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Self signed certificate		1	CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co

192.99.32.127

443

Certificate/chain invalid and wrong name

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

192.99.32.127

443

Certificate/chain invalid and wrong name

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Self signed certificate		1	CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co

9. Certificates

CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co

23.04.2024

23.04.2025
78 days expired

ingress.local - 1 entry

CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co

23.04.2024

23.04.2025
78 days expired

ingress.local - 1 entry

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	00E178E3074EBE187C77FA6882B82830A0
Thumbprint:	AEF1AEE4533D7DD39C9416C31AF2CE1ED40FFC1F
SHA256 / Certificate:	p5tgBbFxf9R9hrbwUzmtDfwuey/cCC8Lq9RoRDd010I=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	594216e0387a4bd0e67ac68198ea3e505b0c8e94b527823b426f88b3fdafcb1f
SHA256 hex / Subject Public Key Information (SPKI):	594216e0387a4bd0e67ac68198ea3e505b0c8e94b527823b426f88b3fdafcb1f (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1)

UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

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

Issuer				last 7 days	active	num Certs
CN=R10, O=Let's Encrypt, C=US				0	0	1
CN=R11, O=Let's Encrypt, C=US				0	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
17436870622 precert	CN=R10, O=Let's Encrypt, C=US	2025-03-27 04:11:10	2025-06-25 03:11:09	docker.datasense-group.fr, jenkins.datasense-group.fr, k8s.datasense-group.fr, minio-console-int.datasense-group.fr, minio-int.datasense-group.fr, nexus.datasense-group.fr, pct-api-int.datasense-group.fr, pct-front-int.datasense-group.fr, pct-storage-int.datasense-group.fr 9 entries
16425587778 precert	CN=R11, O=Let's Encrypt, C=US	2025-01-26 05:08:47	2025-04-26 04:08:46	docker.datasense-group.fr, jenkins.datasense-group.fr, k8s.datasense-group.fr, minio-console-int.datasense-group.fr, minio-int.datasense-group.fr, nexus.datasense-group.fr, pct-api-int.datasense-group.fr, pct-front-int.datasense-group.fr, pct-storage-int.datasense-group.fr 9 entries

11. Html-Content - Entries

Summary

							Subresource Integrity (SRI)
Domainname	HtmlElement	rel/property	∑	∑ size	∑ problems	∑ int.	∑ ext.	∑ Origin poss.	∑ SRI ParseErrors	∑ SRI valid	∑ SRI missing
https://192.99.32.127/ 192.99.32.127	link	stylesheet	2		0			0	0	0
	link	other	1		0			0	0	0
	meta	other	2		0			0	0	0
	script		4		0			0	0	0

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

Domainname	Html-Element	name/equiv/ property/rel	href/src/content
https://192.99.32.127/ 192.99.32.127	link	icon	assets/images/kubernetes-logo.png	1	ok
					ok


	link	stylesheet	styles.243e6d874431c8e8.css	2	ok
					ok


	meta	charset	utf-8	1	ok
					ok


	meta	viewport	width=device-width	1	ok
					ok


	script	src	en.main.3550e3edca7d0ed8.js	1	ok
	Missing defer / async attribute.				ok


	script	src	polyfills.5c84b93f78682d4f.js	1	ok
	Missing defer / async attribute.				ok


	script	src	runtime.134ad7745384bed8.js	1	ok
	Missing defer / async attribute.				ok


	script	src	scripts.2c4f58d7c579cacb.js	1	ok
	Missing defer / async attribute.				ok

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

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: dns101.ovh.net, ns101.ovh.net

QNr.	Domain	Type	NS used
1	net	NS	f.root-servers.net (2001:500:2f::f)
	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	dns101.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	ns101.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	dns101.ovh.net: 213.251.188.145	A	dns10.ovh.net (2001:41d0:1:4a81::1)
5	dns101.ovh.net: 2001:41d0:1:4a91::1	AAAA	dns10.ovh.net (2001:41d0:1:4a81::1)
6	ns101.ovh.net: 213.251.128.145	A	dns10.ovh.net (2001:41d0:1:4a81::1)
7	ns101.ovh.net: 2001:41d0:1:1991::1	AAAA	dns10.ovh.net (2001:41d0:1:4a81::1)

14. CAA - Entries

Domainname	flag	Value	∑ Queries
pct-front-int.datasense-group.fr			1
dev.datasense-group.fr	0	no CAA entry found	1
datasense-group.fr	0	no CAA entry found	1
	0	no CAA entry found	1
fr	0	no CAA entry found	1
	0	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
datasense-group.fr	ok	1
pct-front-int.datasense-group.fr		1
_acme-challenge.dev.datasense-group.fr	Name Error - The domain name does not exist	1
_acme-challenge.pct-front-int.datasense-group.fr	Name Error - The domain name does not exist	1
_acme-challenge.dev.datasense-group.fr.dev.datasense-group.fr	Name Error - The domain name does not exist	1
_acme-challenge.pct-front-int.datasense-group.fr.datasense-group.fr	Name Error - The domain name does not exist	1
_acme-challenge.pct-front-int.datasense-group.fr.pct-front-int.datasense-group.fr	Name Error - The domain name does not exist	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status	Description
SPF	TXT	pct-front-int.datasense-group.fr					32768	TXT expected, but CNAME found. CNAME not allowed, only TXT queries are allowed. See RFC 7208, 4.4.

17. Cipher Suites

Summary
Domain	IP	Port	num Ciphers	time	Std.Protocol	Forward Secrecy
pct-front-int.datasense-group.fr	192.99.32.127	443	3 Ciphers	63.49 sec		0 without, 3 FS	100.00 %
Complete		1	3 Ciphers 3.00 Ciphers/Check	63.49 sec	63.49 sec/Check	0 without, 3 FS	100.00 %

Details
Domain	IP	Port	Cipher (OpenSsl / IANA)
pct-front-int.datasense-group.fr	192.99.32.127	443	ECDHE-RSA-CHACHA20-POLY1305		(Secure)	TLSv1.2	0xCC,0xA8	FS
3 Ciphers, 63.49 sec			TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
			ECDH		RSA	CHACHA20/POLY1305(256)	AEAD
			ECDHE-RSA-AES256-GCM-SHA384		(Secure)	TLSv1.2	0xC0,0x30	FS
			TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
			ECDH		RSA	AESGCM(256)	AEAD
			ECDHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0xC0,0x2F	FS
			TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
			ECDH		RSA	AESGCM(128)	AEAD

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=cf9db3bc-df50-4242-8b08-abe5dd16a14c

Last Result: https://check-your-website.server-daten.de/?q=pct-front-int.datasense-group.fr - 2025-07-05 20:01:32

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

<a href="https://check-your-website.server-daten.de/?q=pct-front-int.datasense-group.fr" target="_blank">Check this Site: pct-front-int.datasense-group.fr</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=pct-front-int.datasense-group.fr

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

Older results

1. IP-Addresses

2. DNSSEC

3. Name Servers

4. SOA-Entries

5. Screenshots

Mobile- and other Chrome-Checks

6. Url-Checks

7. Comments

1. General Results, most used to calculate the result

2. Header-Checks

3. DNS- and NameServer - Checks

4. Content- and Performance-critical Checks

8. Connections

9. Certificates

10. Last Certificates - Certificate Transparency Log Check

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

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

11. Html-Content - Entries

Summary

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

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

13. Nameserver - IP-Adresses

14. CAA - Entries

15. TXT - Entries

16. DomainService - Entries

17. Cipher Suites

18. Portchecks