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

0 in Queue, 0 of max. 4 Checks (18:54:22)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

H

 

Http as Destination - no encryption

 

Checked:
03.09.2025 05:45:42

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
emi.re
A
213.186.33.19
Roubaix/Hauts-de-France/France (FR) - OVH SAS
Hostname: cluster010.hosting.ovh.net
yes
1
0

AAAA
2001:41d0:1:1b00:213:186:33:19
Roubaix/Hauts-de-France/France (FR) - OVH SAS

yes


www.emi.re
A
213.186.33.19
Roubaix/Hauts-de-France/France (FR) - OVH SAS
Hostname: cluster010.hosting.ovh.net
yes
1
0

AAAA
2001:41d0:1:1b00:213:186:33:19
Roubaix/Hauts-de-France/France (FR) - OVH SAS

yes


*.emi.re
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: 20.09.2025, 00:00:00 +, Signature-Inception: 30.08.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: re

re
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 61047, DigestType 2 and Digest amVG9EyGgMcFYS+XIqWR27uIvw1A6J4ctF+tGO7j1Oo=






1 RRSIG RR to validate DS RR found






RRSIG-Owner re., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.09.2025, 17:00:00 +, Signature-Inception: 02.09.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 43891, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner re., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 30.09.2025, 04:44:08 +, Signature-Inception: 31.08.2025, 04:15:02 +, KeyTag 61047, Signer-Name: re






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






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



Zone: emi.re

emi.re
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 8872, DigestType 2 and Digest jbUOvF7wyVDnQ6kBjjfwtJeHHgKwBIllT4SMz5n38qs=






1 RRSIG RR to validate DS RR found






RRSIG-Owner emi.re., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.09.2025, 05:11:53 +, Signature-Inception: 19.08.2025, 04:29:10 +, KeyTag 43891, Signer-Name: re






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 63349, Flags 256






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner emi.re., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 8872, Signer-Name: emi.re






RRSIG-Owner emi.re., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






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






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






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






RRSIG Type 1 validates the A - Result: 213.186.33.19
Validated: RRSIG-Owner emi.re., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






RRSIG Type 16 validates the TXT - Result: 1|www.emi.re v=spf1 include:mx.ovh.com ~all google-site-verification=kmlgtlI0Q0AWeaB-76XWwT_yL1mtp6Yz07JN047z7y8
Validated: RRSIG-Owner emi.re., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






RRSIG Type 28 validates the AAAA - Result: 2001:41D0:0001:1B00:0213:0186:0033:0019
Validated: RRSIG-Owner emi.re., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "67hqpns6ffb5fjlj8b51cgg61n7nnrt4" equal the hashed NSEC3-owner "67hqpns6ffb5fjlj8b51cgg61n7nnrt4" and the hashed NextOwner "6nppd9ct4uh5ddhki3759eec0d6a18i4". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 67hqpns6ffb5fjlj8b51cgg61n7nnrt4.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.emi.re) sends a valid NSEC3 RR as result with the hashed owner name "qp98hfga880tb4t27aleod74tjj5u7u1" (unhashed: _tcp.emi.re). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner qp98hfga880tb4t27aleod74tjj5u7u1.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






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 "ad6oto1pp61c0dbsrh58490pqg8movhq" (unhashed: *._tcp.emi.re) with the owner "6nppd9ct4uh5ddhki3759eec0d6a18i4" and the NextOwner "ak1iefe8d1hot7dg6tvm5d8hin4m6inq". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner 6nppd9ct4uh5ddhki3759eec0d6a18i4.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






Status: Good. NXDomain-Proof required and found.






TLSA-Query (_443._tcp.emi.re) sends a valid NSEC3 RR as result with the owner name "r1elaihmih4d1bgc7sk9p0t2i6fii8jr" greater the NextOwner-Name "5ob42vjlihcr2g5l438k07qvk9a4pj6d", so the NSEC3 covers the end of the zone. The hashed query name "rddpast47sd3gr2ucf7l842v4fembcfm" comes after the hashed Owner, so the zone confirmes the not-existence of that TLSA RR.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner r1elaihmih4d1bgc7sk9p0t2i6fii8jr.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "67hqpns6ffb5fjlj8b51cgg61n7nnrt4" equal the hashed NSEC3-owner "67hqpns6ffb5fjlj8b51cgg61n7nnrt4" and the hashed NextOwner "6nppd9ct4uh5ddhki3759eec0d6a18i4". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 67hqpns6ffb5fjlj8b51cgg61n7nnrt4.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






Status: Good. NoData-Proof required and found.



Zone: www.emi.re

www.emi.re
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 "dufgbi9fh7j0565lggmgms698j8atg5k" between the hashed NSEC3-owner "dufgbi9fh7j0565lggmgms698j8atg5k" and the hashed NextOwner "fo9qc93m8v655l0bpbsn7pjdap05dbg3". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, MX, TXT, AAAA, RRSIG Validated: RRSIG-Owner dufgbi9fh7j0565lggmgms698j8atg5k.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






RRSIG Type 1 validates the A - Result: 213.186.33.19
Validated: RRSIG-Owner www.emi.re., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






RRSIG Type 16 validates the TXT - Result: l|fr 3|welcome
Validated: RRSIG-Owner www.emi.re., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






RRSIG Type 28 validates the AAAA - Result: 2001:41D0:0001:1B00:0213:0186:0033:0019
Validated: RRSIG-Owner www.emi.re., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "dufgbi9fh7j0565lggmgms698j8atg5k" equal the hashed NSEC3-owner "dufgbi9fh7j0565lggmgms698j8atg5k" and the hashed NextOwner "fo9qc93m8v655l0bpbsn7pjdap05dbg3". 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, MX, TXT, AAAA, RRSIG Validated: RRSIG-Owner dufgbi9fh7j0565lggmgms698j8atg5k.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.www.emi.re) sends a valid NSEC3 RR as result with the hashed owner name "dufgbi9fh7j0565lggmgms698j8atg5k" (unhashed: www.emi.re). So that's the Closest Encloser of the query name.
Bitmap: A, MX, TXT, AAAA, RRSIG Validated: RRSIG-Owner dufgbi9fh7j0565lggmgms698j8atg5k.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "vhjt2dbr2qmhgtj647jhptmfq133lu7s" (unhashed: _tcp.www.emi.re) with the owner "r1elaihmih4d1bgc7sk9p0t2i6fii8jr" and the NextOwner "5ob42vjlihcr2g5l438k07qvk9a4pj6d". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner r1elaihmih4d1bgc7sk9p0t2i6fii8jr.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






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 "9akj9p27n9o3ksp07bhdijmcv4ck1r6a" (unhashed: *.www.emi.re) with the owner "6nppd9ct4uh5ddhki3759eec0d6a18i4" and the NextOwner "ak1iefe8d1hot7dg6tvm5d8hin4m6inq". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner 6nppd9ct4uh5ddhki3759eec0d6a18i4.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "dufgbi9fh7j0565lggmgms698j8atg5k" equal the hashed NSEC3-owner "dufgbi9fh7j0565lggmgms698j8atg5k" and the hashed NextOwner "fo9qc93m8v655l0bpbsn7pjdap05dbg3". 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, MX, TXT, AAAA, RRSIG Validated: RRSIG-Owner dufgbi9fh7j0565lggmgms698j8atg5k.emi.re., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.09.2025, 12:00:08 +, Signature-Inception: 30.08.2025, 12:00:08 +, KeyTag 63349, Signer-Name: emi.re






Status: Good. NoData-Proof required and found.

 

3. Name Servers

DomainNameserverNS-IP
www.emi.re
•  dns108.ovh.net
•
emi.re
•  dns108.ovh.net
5.196.41.157
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•

• 
2001:41d0:d01:200::2
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•

•  ns108.ovh.net
5.135.66.229
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•

• 
2001:41d0:b00:fc00::2
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•
re
•  a.nic.fr


•  d.nic.fr
•

•  f.ext.nic.fr
•

•  g.ext.nic.fr
•

 

4. SOA-Entries


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


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


Domain:emi.re
Zone-Name:emi.re
Primary:dns108.ovh.net
Mail:tech.ovh.net
Serial:2025083000
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:4


Domain:www.emi.re
Zone-Name:emi.re
Primary:dns108.ovh.net
Mail:tech.ovh.net
Serial:2025083000
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:1


5. Screenshots

Startaddress: https://emi.re/, address used: https://emi.re/, Screenshot created 2025-09-03 05:49:59 +00:0

 

Mobil (412px x 732px)

 

1098 milliseconds

 

Screenshot mobile - https://emi.re/
Mobil + Landscape (732px x 412px)

 

1085 milliseconds

 

Screenshot mobile landscape - https://emi.re/
Screen (1280px x 1680px)

 

1443 milliseconds

 

Screenshot Desktop - https://emi.re/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport397717
content Size4026985

 

Fatal: Horizontal scrollbar detected. Content-size width is greater then visual Viewport width.

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://emi.re/
213.186.33.19 gzip used - 11577 / 56053 - 79.35 %
200

Html is minified: 154.17 %
0.093
H
Date: Wed, 03 Sep 2025 03:46:10 GMT
Server: OVHcloud
Accept-Ranges: bytes
Vary: Accept-Encoding
x-iplb-request-id: 55D702E3:FC7E_D5BA2113:0050_68B7BA02_16D68:4CEE
x-iplb-instance: 51814
Content-Type: text/html
Content-Length: 11577
Content-Encoding: gzip

• http://emi.re/
2001:41d0:1:1b00:213:186:33:19 gzip used - 11577 / 56053 - 79.35 %
200

Html is minified: 154.17 %
0.056
H
Date: Wed, 03 Sep 2025 03:46:10 GMT
Server: OVHcloud
Accept-Ranges: bytes
Vary: Accept-Encoding
x-iplb-request-id: 2A010238301B00000000000000001227:FC82_200141D000011B000213018600330019:0050_68B7BA02_2B3EC:2087
x-iplb-instance: 51833
Content-Type: text/html
Content-Length: 11577
Content-Encoding: gzip

• http://www.emi.re/
213.186.33.19 gzip used - 11577 / 56053 - 79.35 %
200

Html is minified: 154.17 %
0.037
H
Date: Wed, 03 Sep 2025 03:46:10 GMT
Server: OVHcloud
Accept-Ranges: bytes
Vary: Accept-Encoding
x-iplb-request-id: 55D702E3:FC7E_D5BA2113:0050_68B7BA02_16E21:4CEE
x-iplb-instance: 51814
Content-Type: text/html
Content-Length: 11577
Content-Encoding: gzip

• http://www.emi.re/
2001:41d0:1:1b00:213:186:33:19 gzip used - 11577 / 56053 - 79.35 %
200

Html is minified: 154.17 %
0.040
H
Date: Wed, 03 Sep 2025 03:46:10 GMT
Server: OVHcloud
Accept-Ranges: bytes
Vary: Accept-Encoding
x-iplb-request-id: 2A010238301B00000000000000001227:FC82_200141D000011B000213018600330019:0050_68B7BA02_2B493:2087
x-iplb-instance: 51833
Content-Type: text/html
Content-Length: 11577
Content-Encoding: gzip

• https://emi.re/
213.186.33.19 gzip used - 11577 / 56053 - 79.35 %
200

Html is minified: 154.17 %
2.283
B
Date: Wed, 03 Sep 2025 03:46:10 GMT
Connection: keep-alive
Server: OVHcloud
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Type: text/html
Content-Length: 11577
Content-Encoding: gzip

• https://emi.re/
2001:41d0:1:1b00:213:186:33:19 gzip used - 11577 / 56053 - 79.35 %
200

Html is minified: 154.17 %
2.227
B
Date: Wed, 03 Sep 2025 03:46:14 GMT
Connection: keep-alive
Server: OVHcloud
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Type: text/html
Content-Length: 11577
Content-Encoding: gzip

• https://www.emi.re/
213.186.33.19 gzip used - 11577 / 56053 - 79.35 %
200

Html is minified: 154.17 %
2.310
B
Date: Wed, 03 Sep 2025 03:46:18 GMT
Connection: keep-alive
Server: OVHcloud
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Type: text/html
Content-Length: 11577
Content-Encoding: gzip

• https://www.emi.re/
2001:41d0:1:1b00:213:186:33:19 gzip used - 11577 / 56053 - 79.35 %
200

Html is minified: 154.17 %
2.203
B
Date: Wed, 03 Sep 2025 03:46:22 GMT
Connection: keep-alive
Server: OVHcloud
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Type: text/html
Content-Length: 11577
Content-Encoding: gzip

• http://emi.re/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
213.186.33.19
404

Html is minified: 102.61 %
0.053
A
Not Found
Visible Content:
Date: Wed, 03 Sep 2025 03:46:25 GMT
Server: OVHcloud
x-iplb-request-id: 55D702E3:FCC3_D5BA2113:0050_68B7BA11_48B8:6A59
x-iplb-instance: 51794
Content-Type: text/html; charset=iso-8859-1
Content-Length: 315

• http://emi.re/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:41d0:1:1b00:213:186:33:19
404

Html is minified: 102.61 %
0.044
A
Not Found
Visible Content:
Date: Wed, 03 Sep 2025 03:46:25 GMT
Server: OVHcloud
x-iplb-request-id: 2A010238301B00000000000000001227:FCC7_200141D000011B000213018600330019:0050_68B7BA11_2D9B1:2087
x-iplb-instance: 51833
Content-Type: text/html; charset=iso-8859-1
Content-Length: 315

• http://www.emi.re/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
213.186.33.19
404

Html is minified: 102.61 %
0.027
A
Not Found
Visible Content:
Date: Wed, 03 Sep 2025 03:46:25 GMT
Server: OVHcloud
x-iplb-request-id: 55D702E3:FCC3_D5BA2113:0050_68B7BA11_48F8:6A59
x-iplb-instance: 51794
Content-Type: text/html; charset=iso-8859-1
Content-Length: 315

• http://www.emi.re/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:41d0:1:1b00:213:186:33:19
404

Html is minified: 102.61 %
0.027
A
Not Found
Visible Content:
Date: Wed, 03 Sep 2025 03:46:25 GMT
Server: OVHcloud
x-iplb-request-id: 2A010238301B00000000000000001227:FCC7_200141D000011B000213018600330019:0050_68B7BA11_2D9EC:2087
x-iplb-instance: 51833
Content-Type: text/html; charset=iso-8859-1
Content-Length: 315

• https://213.186.33.19/
213.186.33.19
404

Html is minified: 164.99 %
2.283
N-
Not Found
Certificate error: RemoteCertificateNameMismatch
Date: Wed, 03 Sep 2025 03:46:26 GMT
Transfer-Encoding: chunked
Connection: keep-alive
X-OVH-Webhosting-Id: a3e14efd1d0cbfb84e2a4dee508554b9
Pragma: no-cache
Cache-Control: no-store, must-revalidate, no-cache, post-check=0, pre-check=0
Server: OVHcloud
Content-Type: text/html; charset=utf8
Content-Length: 4958

• https://[2001:41d0:0001:1b00:0213:0186:0033:0019]/
2001:41d0:1:1b00:213:186:33:19
404

Html is minified: 164.84 %
2.210
N-
Not Found
Certificate error: RemoteCertificateNameMismatch
Date: Wed, 03 Sep 2025 03:46:29 GMT
Transfer-Encoding: chunked
Connection: keep-alive
X-OVH-Webhosting-Id: a57231348155d85c21683e8d632077eb
Pragma: no-cache
Cache-Control: no-store, must-revalidate, no-cache, post-check=0, pre-check=0
Server: OVHcloud
Content-Type: text/html; charset=utf8
Content-Length: 4965

 

7. Comments


1. General Results, most used to calculate the result

Aname "emi.re" is domain, public suffix is ".re", top-level-domain is ".re", top-level-domain-type is "country-code", Country is Réunion, tld-manager is "Association Française pour le Nommage Internet en Coopération (A.F.N.I.C.)", num .re-domains preloaded: 138 (complete: 276475)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: emi.re has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.emi.re has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: emi.re has 1 ipv4, 1 ipv6 addresses
AGood: Ipv4 and Ipv6 addresses per domain name found: www.emi.re has 1 ipv4, 1 ipv6 addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):4 complete Content-Type - header (14 urls)
http://emi.re/ 213.186.33.19


Url with incomplete Content-Type - header - missing charset
http://emi.re/ 2001:41d0:1:1b00:213:186:33:19


Url with incomplete Content-Type - header - missing charset
http://www.emi.re/ 213.186.33.19


Url with incomplete Content-Type - header - missing charset
http://www.emi.re/ 2001:41d0:1:1b00:213:186:33:19


Url with incomplete Content-Type - header - missing charset
https://emi.re/ 213.186.33.19


Url with incomplete Content-Type - header - missing charset
https://emi.re/ 2001:41d0:1:1b00:213:186:33:19


Url with incomplete Content-Type - header - missing charset
https://www.emi.re/ 213.186.33.19


Url with incomplete Content-Type - header - missing charset
https://www.emi.re/ 2001:41d0:1:1b00:213:186:33:19


Url with incomplete Content-Type - header - missing charset
Ahttps://213.186.33.19/ 213.186.33.19


Url with Content-Type - parse error: Header: text/html; charset=utf8, parse error: charset=utf8
Ahttps://[2001:41d0:0001:1b00:0213:0186:0033:0019]/ 2001:41d0:1:1b00:213:186:33:19


Url with Content-Type - parse error: Header: text/html; charset=utf8, parse error: charset=utf8
Bhttps://emi.re/ 213.186.33.19
200

Missing HSTS-Header
Bhttps://emi.re/ 2001:41d0:1:1b00:213:186:33:19
200

Missing HSTS-Header
Bhttps://www.emi.re/ 213.186.33.19
200

Missing HSTS-Header
Bhttps://www.emi.re/ 2001:41d0:1:1b00:213:186:33:19
200

Missing HSTS-Header
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Mhttps://213.186.33.19/ 213.186.33.19
404

Misconfiguration - main pages should never send http status 400 - 499
Mhttps://[2001:41d0:0001:1b00:0213:0186:0033:0019]/ 2001:41d0:1:1b00:213:186:33:19
404

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://213.186.33.19/ 213.186.33.19
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://[2001:41d0:0001:1b00:0213:0186:0033:0019]/ 2001:41d0:1:1b00:213:186:33:19
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain emi.re, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.emi.re, 2 ip addresses.
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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain emi.re, 2 ip addresses.
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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain www.emi.re, 2 ip addresses.
BNo _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.emi.re

2. Header-Checks

Femi.re 213.186.33.19
Content-Security-Policy
Critical: Missing Header:
Femi.re 213.186.33.19
X-Content-Type-Options
Critical: Missing Header:
Femi.re 213.186.33.19
Referrer-Policy
Critical: Missing Header:
Femi.re 213.186.33.19
Permissions-Policy
Critical: Missing Header:
Bemi.re 213.186.33.19
Cross-Origin-Embedder-Policy
Info: Missing Header
Bemi.re 213.186.33.19
Cross-Origin-Opener-Policy
Info: Missing Header
Bemi.re 213.186.33.19
Cross-Origin-Resource-Policy
Info: Missing Header
Femi.re 2001:41d0:1:1b00:213:186:33:19
Content-Security-Policy
Critical: Missing Header:
Femi.re 2001:41d0:1:1b00:213:186:33:19
X-Content-Type-Options
Critical: Missing Header:
Femi.re 2001:41d0:1:1b00:213:186:33:19
Referrer-Policy
Critical: Missing Header:
Femi.re 2001:41d0:1:1b00:213:186:33:19
Permissions-Policy
Critical: Missing Header:
Bemi.re 2001:41d0:1:1b00:213:186:33:19
Cross-Origin-Embedder-Policy
Info: Missing Header
Bemi.re 2001:41d0:1:1b00:213:186:33:19
Cross-Origin-Opener-Policy
Info: Missing Header
Bemi.re 2001:41d0:1:1b00:213:186:33:19
Cross-Origin-Resource-Policy
Info: Missing Header
Fwww.emi.re 213.186.33.19
Content-Security-Policy
Critical: Missing Header:
Fwww.emi.re 213.186.33.19
X-Content-Type-Options
Critical: Missing Header:
Fwww.emi.re 213.186.33.19
Referrer-Policy
Critical: Missing Header:
Fwww.emi.re 213.186.33.19
Permissions-Policy
Critical: Missing Header:
Bwww.emi.re 213.186.33.19
Cross-Origin-Embedder-Policy
Info: Missing Header
Bwww.emi.re 213.186.33.19
Cross-Origin-Opener-Policy
Info: Missing Header
Bwww.emi.re 213.186.33.19
Cross-Origin-Resource-Policy
Info: Missing Header
Fwww.emi.re 2001:41d0:1:1b00:213:186:33:19
Content-Security-Policy
Critical: Missing Header:
Fwww.emi.re 2001:41d0:1:1b00:213:186:33:19
X-Content-Type-Options
Critical: Missing Header:
Fwww.emi.re 2001:41d0:1:1b00:213:186:33:19
Referrer-Policy
Critical: Missing Header:
Fwww.emi.re 2001:41d0:1:1b00:213:186:33:19
Permissions-Policy
Critical: Missing Header:
Bwww.emi.re 2001:41d0:1:1b00:213:186:33:19
Cross-Origin-Embedder-Policy
Info: Missing Header
Bwww.emi.re 2001:41d0:1:1b00:213:186:33:19
Cross-Origin-Opener-Policy
Info: Missing Header
Bwww.emi.re 2001:41d0:1:1b00:213:186:33:19
Cross-Origin-Resource-Policy
Info: Missing Header

3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
AGood: 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.
AInfo:: 2 different Name Servers found: dns108.ovh.net, ns108.ovh.net, 2 Name Servers included in Delegation: dns108.ovh.net, ns108.ovh.net, 2 Name Servers included in 1 Zone definitions: dns108.ovh.net, ns108.ovh.net, 1 Name Servers listed in SOA.Primary: dns108.ovh.net.
AGood: Only one SOA.Primary Name Server found.: dns108.ovh.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns108.ovh.net.
AGood: 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: dns108.ovh.net, ns108.ovh.net
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: 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
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 5., 2 different subnets (first two Bytes): 5.135., 5.196., 2 different subnets (first three Bytes): 5.135.66., 5.196.41.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:41d0:, 2 different subnets (first three blocks): 2001:41d0:0b00:, 2001:41d0:0d01:, 2 different subnets (first four blocks): 2001:41d0:0b00:fc00:, 2001:41d0:0d01:0200:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: 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

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
https://emi.re/ 213.186.33.19
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.
https://emi.re/ 2001:41d0:1:1b00:213:186:33:19
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.
https://www.emi.re/ 213.186.33.19
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.
https://www.emi.re/ 2001:41d0:1:1b00:213:186:33:19
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.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
AInfo: No img element found, no alt attribute checked
AGood: 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
https://213.186.33.19/ 213.186.33.19
404
2.283 seconds
Warning: 404 needs more then one second
https://[2001:41d0:0001:1b00:0213:0186:0033:0019]/ 2001:41d0:1:1b00:213:186:33:19
404
2.210 seconds
Warning: 404 needs more then one second
ADuration: 264103 milliseconds, 264.103 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
emi.re
213.186.33.19
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
emi.re
213.186.33.19
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=lisletdelisle.fr


2CN=E5, O=Let's Encrypt, C=US


emi.re
2001:41d0:1:1b00:213:186:33:19
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

emi.re
2001:41d0:1:1b00:213:186:33:19
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=lisletdelisle.fr


2CN=E5, O=Let's Encrypt, C=US


www.emi.re
213.186.33.19
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

www.emi.re
213.186.33.19
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=lisletdelisle.fr


2CN=E5, O=Let's Encrypt, C=US


www.emi.re
2001:41d0:1:1b00:213:186:33:19
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

www.emi.re
2001:41d0:1:1b00:213:186:33:19
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=lisletdelisle.fr


2CN=E5, O=Let's Encrypt, C=US


213.186.33.19
213.186.33.19
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

213.186.33.19
213.186.33.19
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
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
Chain (complete)

1CN=cluster010.hosting.ovh.net


2CN=R12, O=Let's Encrypt, C=US


[2001:41d0:0001:1b00:0213:0186:0033:0019]
2001:41d0:1:1b00:213:186:33:19
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

[2001:41d0:0001:1b00:0213:0186:0033:0019]
2001:41d0:1:1b00:213:186:33:19
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
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
Chain (complete)

1CN=cluster010.hosting.ovh.net


2CN=R12, O=Let's Encrypt, C=US

 

9. Certificates

1.
1.
CN=lisletdelisle.fr
09.07.2025
07.10.2025
281 days expired		emi.re, iago.re, lisletdelisle.fr, peapea.re, www.emi.re, www.iago.re, www.lisletdelisle.fr, www.peapea.re - 8 entries
1.
1.
CN=lisletdelisle.fr
09.07.2025

07.10.2025
281 days expired


emi.re, iago.re, lisletdelisle.fr, peapea.re, www.emi.re, www.iago.re, www.lisletdelisle.fr, www.peapea.re - 8 entries

KeyalgorithmEC Public Key (256 bit, prime256v1)
Signatur:ECDSA SHA384
Serial Number:06850605FAC648A5B170B2BD4E26C31AB9D3
Thumbprint:9672299F6F4B0D3B8031CE006E2EA373C99FC4AA
SHA256 / Certificate:++Gv6L2hF1maPJsLP5AbVj+nslTzC/5j8wn83Rr0u9E=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):5ebb2fb739c6e10356b43eb1ef5de542ebeb917846915c5edd61f2b80966aac8
SHA256 hex / Subject Public Key Information (SPKI):5ebb2fb739c6e10356b43eb1ef5de542ebeb917846915c5edd61f2b80966aac8 (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:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=E5, O=Let's Encrypt, C=US
13.03.2024
13.03.2027
expires in 241 days

2.
CN=E5, O=Let's Encrypt, C=US
13.03.2024

13.03.2027
expires in 241 days




KeyalgorithmEC Public Key (384 bit, secp384r1)
Signatur:SHA256 With RSA-Encryption
Serial Number:00838F6C63CEB1398C6206628315C9FDDE
Thumbprint:5F28D9C589EE4BF31A11B78C72B8D13F079DDC45
SHA256 / Certificate:Xf2zzzGybyPYfAnzoM72QvZAaan7fP4pJwu13A8eFrs=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):3586d4ecf070578cbd27aedce20b964e48bc149faeb9dad72f46b857869172b8
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3246 days

3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3246 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
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:




2.
1.
CN=cluster010.hosting.ovh.net
27.08.2025
25.11.2025
232 days expired		cluster010.hosting.ovh.net - 1 entry
2.
1.
CN=cluster010.hosting.ovh.net
27.08.2025

25.11.2025
232 days expired


cluster010.hosting.ovh.net - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:05ACEAF00C0445FB156941331328A42C5FC9
Thumbprint:D6162105DE29C62CD5F5AF39FDA8B3E476EE7ECE
SHA256 / Certificate:TdQFsQuZL08Zv9y/w6FwCiXyIwSd5z3pegoAICINZUA=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):d28a0c5cba6e9222b4d1acfe3b52a2f5510a232057bc20a704c322fe9c355341
SHA256 hex / Subject Public Key Information (SPKI):d28a0c5cba6e9222b4d1acfe3b52a2f5510a232057bc20a704c322fe9c355341 (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:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=R12, O=Let's Encrypt, C=US
13.03.2024
13.03.2027
expires in 241 days

2.
CN=R12, O=Let's Encrypt, C=US
13.03.2024

13.03.2027
expires in 241 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00C212324B70A9B49171DC40F7E285263C
Thumbprint:EE44782835D8FB31394DA5CEB840DC93849BCF5A
SHA256 / Certificate:Ex/Od4QBaJmloAIDqe/IDxjrvXVYBxftwVU1gJMINuw=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):919c0df7a787b597ed056ace654b1de9c0387acf349f73734a4fd7b58cf612a4
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3246 days

3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3246 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
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:




 

10. Last Certificates - Certificate Transparency Log Check

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

Issuerlast 7 daysactivenum Certs
CN=E5, O=Let's Encrypt, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
11047317768
leaf cert		CN=E5, O=Let's Encrypt, C=US
2025-07-08 22:26:53
2025-10-06 22:26:52
emi.re, iago.re, lisletdelisle.fr, peapea.re, www.emi.re, www.iago.re, www.lisletdelisle.fr, www.peapea.re - 8 entries


 

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

Issuerlast 7 daysactivenum Certs
CN=E5, O=Let's Encrypt, C=US
0
0
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
19538649018
leaf cert		CN=E5, O=Let's Encrypt, C=US
2025-07-08 20:26:53
2025-10-06 20:26:52
emi.re, iago.re, lisletdelisle.fr, peapea.re, www.emi.re, www.iago.re, www.lisletdelisle.fr, www.peapea.re
8 entries


18101253554
precert		CN=E5, O=Let's Encrypt, C=US
2025-04-28 00:20:06
2025-07-27 00:20:05
emi.re, iago.re, lisletdelisle.fr, peapea.re, www.emi.re, www.iago.re, www.lisletdelisle.fr, www.peapea.re
8 entries


 

11. Html-Content - Entries

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

 

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

Url used (first standard-https-result with http status 200): https://emi.re/

Summary

Good: No non-document-errors
2 errors
0 warnings

TypeMessagenum found
1.errorStray end tag button.1
2.errorDuplicate attribute id.1

Details


TypeMessage + Sample
1errorStray end tag button.

From line 903, column 25 to line 903, column 33

</button>
2errorDuplicate attribute id.

From line 912, column 59 to line 912, column 59

s="btnNoDYS" id="btnNoDys"

 

13. Nameserver - IP-Adresses

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

 

QNr.DomainTypeNS used
1
net
NS
a.root-servers.net (2001:503:ba3e::2:30)

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
dns108.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:d00:6100::2, 5.135.85.109

Answer: dns11.ovh.net
2001:41d0:d00:f000::2, 5.135.86.61

Answer: dns12.ovh.net
2001:41d0:d00:f100::2, 5.135.86.81

Answer: dns13.ovh.net
2001:41d0:d00:f200::2, 5.135.98.29

Answer: dns15.ovh.net
2001:41d0:d00:f400::2, 5.135.110.101

Answer: ns10.ovh.net
2001:41d0:b00:3a00::2, 5.39.20.253

Answer: ns11.ovh.net
2001:41d0:b00:d000::2, 5.39.27.169

Answer: ns12.ovh.net
2001:41d0:b00:eb00::2, 5.39.102.21

Answer: ns13.ovh.net
2001:41d0:b00:ec00::2, 5.39.112.241

Answer: ns15.ovh.net
2001:41d0:b00:ee00::2, 5.39.114.9
3
ns108.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:d00:6100::2, 5.135.85.109

Answer: dns11.ovh.net
2001:41d0:d00:f000::2, 5.135.86.61

Answer: dns12.ovh.net
2001:41d0:d00:f100::2, 5.135.86.81

Answer: dns13.ovh.net
2001:41d0:d00:f200::2, 5.135.98.29

Answer: dns15.ovh.net
2001:41d0:d00:f400::2, 5.135.110.101

Answer: ns10.ovh.net
2001:41d0:b00:3a00::2, 5.39.20.253

Answer: ns11.ovh.net
2001:41d0:b00:d000::2, 5.39.27.169

Answer: ns12.ovh.net
2001:41d0:b00:eb00::2, 5.39.102.21

Answer: ns13.ovh.net
2001:41d0:b00:ec00::2, 5.39.112.241

Answer: ns15.ovh.net
2001:41d0:b00:ee00::2, 5.39.114.9
4
dns108.ovh.net: 5.196.41.157
A
dns10.ovh.net (2001:41d0:d00:6100::2)
5
dns108.ovh.net: 2001:41d0:d01:200::2
AAAA
dns10.ovh.net (2001:41d0:d00:6100::2)
6
ns108.ovh.net: 5.135.66.229
A
dns10.ovh.net (2001:41d0:d00:6100::2)
7
ns108.ovh.net: 2001:41d0:b00:fc00::2
AAAA
dns10.ovh.net (2001:41d0:d00:6100::2)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.emi.re
0

no CAA entry found
1
0
emi.re
0

no CAA entry found
1
0
re
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
emi.re
1|www.emi.re
ok
1
0
emi.re
google-site-verification=kmlgtlI0Q0AWeaB-76XWwT_yL1mtp6Yz07JN047z7y8
ok
1
0
emi.re
v=spf1 include:mx.ovh.com ~all
ok
1
0
www.emi.re
3|welcome
ok
1
0
www.emi.re
l|fr
ok
1
0
_acme-challenge.emi.re

Name Error - The domain name does not exist
1
0
_acme-challenge.www.emi.re

Name Error - The domain name does not exist
1
0
_acme-challenge.emi.re.emi.re

Name Error - The domain name does not exist
1
0
_acme-challenge.www.emi.re.emi.re

Name Error - The domain name does not exist
1
0
_acme-challenge.www.emi.re.www.emi.re

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

emi.re
1
mx4.mail.ovh.net
02ok

A


178.32.124.207
01ok

CNAME


00ok
MX

emi.re
10
mx3.mail.ovh.net
02ok

A


91.121.53.175
01ok

CNAME


00ok
MX

www.emi.re
1
mx4.mail.ovh.net
02ok

A


178.32.124.207
01ok

CNAME


00ok
MX

www.emi.re
10
mx3.mail.ovh.net
02ok

A


91.121.53.175
01ok

CNAME


00ok
SPF
TXT
emi.re

v=spf1 include:mx.ovh.com ~all
ok

TXT
mx.ovh.com

v=spf1 ptr:mail-out.ovh.net ptr:mail.ovh.net ip4:8.33.137.105/32 ip4:192.99.77.81/32 ?all
ok

TXT
mx.ovh.com

ptr:mail-out.ovh.net
4096"ptr" is deprecated. Don't use it.

TXT
mx.ovh.com

ptr:mail.ovh.net
4096"ptr" is deprecated. Don't use it.

				 
			

				 
			
17. Cipher Suites
Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
emi.re
213.186.33.19
443
5 Ciphers36.23 sec
0 without, 5 FS
100.00 %
emi.re
2001:41d0:1:1b00:213:186:33:19
443
5 Ciphers31.32 sec
0 without, 5 FS
100.00 %
www.emi.re
213.186.33.19
443
5 Ciphers36.61 sec
0 without, 5 FS
100.00 %
www.emi.re
2001:41d0:1:1b00:213:186:33:19
443
5 Ciphers31.42 sec
0 without, 5 FS
100.00 %
Complete

4
20 Ciphers
5.00 Ciphers/Check		135.57 sec33.89 sec/Check
0 without, 20 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
emi.re
213.186.33.19
443
ECDHE-ECDSA-CHACHA20-POLY1305
 (Recommended)
TLSv1.2
0xCC,0xA9
 FS
5 Ciphers, 

36.23 sec
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
ECDSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-ECDSA-AES256-GCM-SHA384
 (Recommended)
TLSv1.2
0xC0,0x2C
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

ECDH
ECDSA
AESGCM(256)
AEAD




ECDHE-ECDSA-AES128-GCM-SHA256
 (Recommended)
TLSv1.2
0xC0,0x2B
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ECDH
ECDSA
AESGCM(128)
AEAD




ECDHE-ECDSA-AES256-SHA384
 (Weak)
TLSv1.2
0xC0,0x24
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

ECDH
ECDSA
AES(256)
SHA384




ECDHE-ECDSA-AES128-SHA256
 (Weak)
TLSv1.2
0xC0,0x23
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

ECDH
ECDSA
AES(128)
SHA256


2001:41d0:1:1b00:213:186:33:19
443
ECDHE-ECDSA-CHACHA20-POLY1305
 (Recommended)
TLSv1.2
0xCC,0xA9
 FS
5 Ciphers, 

31.32 sec
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
ECDSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-ECDSA-AES256-GCM-SHA384
 (Recommended)
TLSv1.2
0xC0,0x2C
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

ECDH
ECDSA
AESGCM(256)
AEAD




ECDHE-ECDSA-AES128-GCM-SHA256
 (Recommended)
TLSv1.2
0xC0,0x2B
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ECDH
ECDSA
AESGCM(128)
AEAD




ECDHE-ECDSA-AES256-SHA384
 (Weak)
TLSv1.2
0xC0,0x24
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

ECDH
ECDSA
AES(256)
SHA384




ECDHE-ECDSA-AES128-SHA256
 (Weak)
TLSv1.2
0xC0,0x23
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

ECDH
ECDSA
AES(128)
SHA256

www.emi.re
213.186.33.19
443
ECDHE-ECDSA-CHACHA20-POLY1305
 (Recommended)
TLSv1.2
0xCC,0xA9
 FS
5 Ciphers, 

36.61 sec
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
ECDSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-ECDSA-AES256-GCM-SHA384
 (Recommended)
TLSv1.2
0xC0,0x2C
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

ECDH
ECDSA
AESGCM(256)
AEAD




ECDHE-ECDSA-AES128-GCM-SHA256
 (Recommended)
TLSv1.2
0xC0,0x2B
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ECDH
ECDSA
AESGCM(128)
AEAD




ECDHE-ECDSA-AES256-SHA384
 (Weak)
TLSv1.2
0xC0,0x24
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

ECDH
ECDSA
AES(256)
SHA384




ECDHE-ECDSA-AES128-SHA256
 (Weak)
TLSv1.2
0xC0,0x23
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

ECDH
ECDSA
AES(128)
SHA256


2001:41d0:1:1b00:213:186:33:19
443
ECDHE-ECDSA-CHACHA20-POLY1305
 (Recommended)
TLSv1.2
0xCC,0xA9
 FS
5 Ciphers, 

31.42 sec
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
ECDSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-ECDSA-AES256-GCM-SHA384
 (Recommended)
TLSv1.2
0xC0,0x2C
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

ECDH
ECDSA
AESGCM(256)
AEAD




ECDHE-ECDSA-AES128-GCM-SHA256
 (Recommended)
TLSv1.2
0xC0,0x2B
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ECDH
ECDSA
AESGCM(128)
AEAD




ECDHE-ECDSA-AES256-SHA384
 (Weak)
TLSv1.2
0xC0,0x24
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

ECDH
ECDSA
AES(256)
SHA384




ECDHE-ECDSA-AES128-SHA256
 (Weak)
TLSv1.2
0xC0,0x23
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

ECDH
ECDSA
AES(128)
SHA256


				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=f7de4075-76e1-4a1f-8628-642b37240bbe

				 
			


Last Result: https://check-your-website.server-daten.de/?q=emi.re - 2025-09-03 05:45:42

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

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

				 
			

				 
			



Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • 
USt-IdNr.: DE221734518

				 
			


Errors, ideas, questions? Use the 
Contact form • A project using

Server-Daten - Web Database solutions