| 1. General Results, most used to calculate the result |
| A | name "limits.eu" is domain, public suffix is "eu", top-level-domain-type is "country-code", Country is European Union, tld-manager is "EURid vzw/asbl"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: destination is https
|
| A | Good: one preferred version: non-www is preferred
|
| A | Good: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| A | Good: HSTS has includeSubdomains - directive
|
| A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| A | http://limits.eu/ 185.96.4.140
| https://limits.eu/
| Correct redirect http - https with the same domain name
|
| A | http://limits.eu/ 2a02:348:b9:48c::1
| https://limits.eu/
| Correct redirect http - https with the same domain name
|
| A | http://www.limits.eu/ 185.96.4.140
| https://www.limits.eu/
| Correct redirect http - https with the same domain name
|
| A | http://www.limits.eu/ 2a02:348:b9:48c::1
| https://www.limits.eu/
| Correct redirect http - https with the same domain name
|
| N | limits.eu:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | limits.eu:993
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | limits.eu:995
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.limits.eu:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.limits.eu:993
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.limits.eu:995
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 185.96.4.140:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 185.96.4.140:993
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 185.96.4.140:995
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Good: Nameserver supports TCP connections: 4 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 5 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.c-yes.com: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns-01.svc.xl-internetservices.com). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.c-yes.com / 194.60.207.54: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns-01.svc.xl-internetservices.com). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.c-yes.com / 2a02:348:28:cf36::1: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns-01.svc.xl-internetservices.com). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.c-yes.com / 79.170.92.6: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns-03.svc.xl-internetservices.com). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.c-yes.com / 2a02:348:28:cf37::1: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns-02.svc.xl-internetservices.com). COOKIE: ok. CLIENTSUBNET: ok.
|
| A | Good: All SOA have the same Serial Number
|
| Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
|
| 4. Content- and Performance-critical Checks |
| https://limits.eu/404.shtml
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
|
| A | Duration: 76410 milliseconds, 76.410 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)