| 1. General Results, most used to calculate the result |
| A | name "icam1.zidi.in" is subdomain, public suffix is ".in", top-level-domain is ".in", top-level-domain-type is "country-code", Country is India, tld-manager is "National Internet Exchange of India", num .in-domains preloaded: 1234 (complete: 271405)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: icam1.zidi.in has 3 different ip addresses (authoritative).
|
| 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: icam1.zidi.in 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 | https://icam1.zidi.in/ 46.8.9.205
| https://lycur-trd.com/zclkvisitor/a5cba790-6d1a-11f0-9fc9-0afff46d3905/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Correct redirect https to https
|
| A | https://icam1.zidi.in/ 46.8.9.207
| https://lycur-trd.com/zclkvisitor/b3ba8c91-6d1a-11f0-b8d8-0affc905d23b/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Correct redirect https to https
|
| A | https://46.8.9.205/ 46.8.9.205
| https://lycur-trd.com/zclkvisitor/be33d2d9-6d1a-11f0-a9aa-120935a90e17/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Correct redirect https to https
|
| A | Good: 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.
|
| A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| B | https://icam1.zidi.in/ 46.8.9.205
|
| Missing HSTS-Header
|
| B | https://icam1.zidi.in/ 46.8.9.206
|
| Missing HSTS-Header
|
| B | https://icam1.zidi.in/ 46.8.9.207
|
| Missing HSTS-Header
|
| B | https://lycur-trd.com/zclkvisitor/a3cb1cab-6d1a-11f0-be9f-0affd0156053/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
|
| Missing HSTS-Header
|
| B | https://lycur-trd.com/zclkvisitor/a4586886-6d1a-11f0-bfa2-12332dee0675/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
|
| Missing HSTS-Header
|
| B | https://lycur-trd.com/zclkvisitor/a4db0600-6d1a-11f0-a9aa-120935a90e17/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
|
| Missing HSTS-Header
|
| B | https://lycur-trd.com/zclkvisitor/a5cba790-6d1a-11f0-9fc9-0afff46d3905/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
|
| Missing HSTS-Header
|
| B | https://lycur-trd.com/zclkvisitor/b3ba8c91-6d1a-11f0-b8d8-0affc905d23b/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
|
| Missing HSTS-Header
|
| B | https://lycur-trd.com/zclkvisitor/bc7a8a15-6d1a-11f0-8c63-12df9bc812df/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
|
| Missing HSTS-Header
|
| C | Error - no version with Http-Status 200
|
| D | http://icam1.zidi.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.8.9.205
| http://ww53.zidi.in/
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| D | http://icam1.zidi.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.8.9.206
| http://ww53.zidi.in/
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://icam1.zidi.in/ 46.8.9.205
| https://lycur-trd.com/zclkvisitor/a3cb1cab-6d1a-11f0-be9f-0affd0156053/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://icam1.zidi.in/ 46.8.9.206
| https://lycur-trd.com/zclkvisitor/a4586886-6d1a-11f0-bfa2-12332dee0675/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://icam1.zidi.in/ 46.8.9.207
| https://lycur-trd.com/zclkvisitor/a4db0600-6d1a-11f0-a9aa-120935a90e17/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| N | https://icam1.zidi.in/ 46.8.9.205
| https://lycur-trd.com/zclkvisitor/a5cba790-6d1a-11f0-9fc9-0afff46d3905/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://icam1.zidi.in/ 46.8.9.206
| http://ww53.zidi.in/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://icam1.zidi.in/ 46.8.9.207
| https://lycur-trd.com/zclkvisitor/b3ba8c91-6d1a-11f0-b8d8-0affc905d23b/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://46.8.9.205/ 46.8.9.205
| https://lycur-trd.com/zclkvisitor/be33d2d9-6d1a-11f0-a9aa-120935a90e17/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://46.8.9.206/ 46.8.9.206
| https://lycur-trd.com/zclkvisitor/c526ff93-6d1a-11f0-8efd-0affd0f54889/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://46.8.9.207/ 46.8.9.207
| https://lycur-trd.com/zclkvisitor/cc0aea16-6d1a-11f0-8efd-0affd0f54889/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| R | https://icam1.zidi.in/ 46.8.9.206
| http://ww53.zidi.in/
| Redirect to not existing domain
|
| R | http://icam1.zidi.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.8.9.205
| http://ww53.zidi.in/
| Redirect to not existing domain
|
| R | http://icam1.zidi.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.8.9.206
| http://ww53.zidi.in/
| Redirect to not existing domain
|
| X | Fatal error: Nameserver doesn't support TCP connection: x.nic.xyz: Timeout
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain icam1.zidi.in, 3 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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain icam1.zidi.in, 3 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.icam1.zidi.in
|
| 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: matias.ns.cloudflare.com, rosalyn.ns.cloudflare.com, 2 Name Servers included in Delegation: matias.ns.cloudflare.com, rosalyn.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: matias.ns.cloudflare.com, rosalyn.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: matias.ns.cloudflare.com.
|
| A | Good: Only one SOA.Primary Name Server found.: matias.ns.cloudflare.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: matias.ns.cloudflare.com.
|
| 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: 6 Name Servers, 3 different subnets (first Byte): 108., 162., 172., 3 different subnets (first two Bytes): 108.162., 162.159., 172.64., 6 different subnets (first three Bytes): 108.162.194., 108.162.195., 162.159.38., 162.159.44., 172.64.34., 172.64.35.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 12 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 12 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: matias.ns.cloudflare.com: 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: ns.parktons.com / 46.8.8.88: 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: ns.parktons.com / 46.8.8.88: 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: ns.trs-dns.com: 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: ns0.centralnic.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.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.parktons.com / 46.8.9.99: 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: ns2.parktons.com / 46.8.9.99: 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: x.nic.xyz: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (PGXL-PS5KRW-2C7ZTP). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: z.nic.xyz: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (PGXL-PS5KRW-2C7ZTP). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| A | Good: All SOA have the same Serial Number
|
| Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
|
| 4. Content- and Performance-critical Checks |
| https://lycur-trd.com/zclkvisitor/bc7a8a15-6d1a-11f0-8c63-12df9bc812df/b71e37a0-18cb-11ea-9f38-0a157bfa6bfc?campaignid=879b22a0-7c25-11ef-8bf9-0affcf01680d
|
| 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.
|
| 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: 754363 milliseconds, 754.363 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)