| 1. General Results, most used to calculate the result |
| A | name "mail.ab-polymerchemie.de" is subdomain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 9732 (complete: 245733)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: mail.ab-polymerchemie.de has only one ip address.
|
| Warning: Only one ip address found: www.mail.ab-polymerchemie.de 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: mail.ab-polymerchemie.de has no ipv6 address.
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.mail.ab-polymerchemie.de has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://mail.ab-polymerchemie.de/webmail/
| https://mail.ab-polymerchemie.de/webmail/login
| Correct redirect https to https
|
| A | https://mail.ab-polymerchemie.de/ 85.16.68.178
| https://mail.ab-polymerchemie.de/webmail/
| Correct redirect https to https
|
| A | https://www.mail.ab-polymerchemie.de/webmail/
| https://www.mail.ab-polymerchemie.de/webmail/login
| Correct redirect https to https
|
| A | https://www.mail.ab-polymerchemie.de/ 85.16.68.178
| https://www.mail.ab-polymerchemie.de/webmail/
| Correct redirect https to https
|
| A | https://85.16.68.178/ 85.16.68.178
| https://mail.ab-polymerchemie.de/webmail/
| 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (2 urls)
|
| http://mail.ab-polymerchemie.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.16.68.178
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.mail.ab-polymerchemie.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.16.68.178
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://mail.ab-polymerchemie.de/webmail/login
|
| Missing HSTS-Header
|
| B | https://mail.ab-polymerchemie.de/webmail/
|
| Missing HSTS-Header
|
| B | https://mail.ab-polymerchemie.de/ 85.16.68.178
|
| Missing HSTS-Header
|
| B | https://www.mail.ab-polymerchemie.de/webmail/
|
| Missing HSTS-Header
|
| B | https://www.mail.ab-polymerchemie.de/webmail/login
|
| Missing HSTS-Header
|
| B | https://www.mail.ab-polymerchemie.de/ 85.16.68.178
|
| Missing HSTS-Header
|
| D | http://mail.ab-polymerchemie.de/webmail/
| http://mail.ab-polymerchemie.de/webmail/login
| 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://mail.ab-polymerchemie.de/webmail/login
| http://mail.ab-polymerchemie.de/webmail/login/
| 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://mail.ab-polymerchemie.de/ 85.16.68.178
| http://mail.ab-polymerchemie.de/webmail/
| 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://www.mail.ab-polymerchemie.de/webmail/
| http://www.mail.ab-polymerchemie.de/webmail/login
| 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://www.mail.ab-polymerchemie.de/webmail/login
| http://www.mail.ab-polymerchemie.de/webmail/login/
| 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://www.mail.ab-polymerchemie.de/ 85.16.68.178
| http://www.mail.ab-polymerchemie.de/webmail/
| 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.
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| N | https://mail.ab-polymerchemie.de/webmail/login
| https://mail.ab-polymerchemie.de/webmail/login/
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
| N | https://mail.ab-polymerchemie.de/webmail/
| https://mail.ab-polymerchemie.de/webmail/login
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
| N | https://mail.ab-polymerchemie.de/ 85.16.68.178
| https://mail.ab-polymerchemie.de/webmail/
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
| N | https://www.mail.ab-polymerchemie.de/webmail/login
| https://www.mail.ab-polymerchemie.de/webmail/login/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://www.mail.ab-polymerchemie.de/webmail/
| https://www.mail.ab-polymerchemie.de/webmail/login
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://www.mail.ab-polymerchemie.de/ 85.16.68.178
| https://www.mail.ab-polymerchemie.de/webmail/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://85.16.68.178/ 85.16.68.178
| https://mail.ab-polymerchemie.de/webmail/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | www.mail.ab-polymerchemie.de:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | mail.ab-polymerchemie.de:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | www.mail.ab-polymerchemie.de:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | mail.ab-polymerchemie.de:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | mail.ab-polymerchemie.de:587
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | www.mail.ab-polymerchemie.de:587
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| O | mail.ab-polymerchemie.de / 85.16.68.178 / 25
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 8 Cipher Suites without Forward Secrecy found
|
| O | mail.ab-polymerchemie.de / 85.16.68.178 / 443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found
|
| O | mail.ab-polymerchemie.de / 85.16.68.178 / 465
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 8 Cipher Suites without Forward Secrecy found
|
| O | mail.ab-polymerchemie.de / 85.16.68.178 / 587
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 8 Cipher Suites without Forward Secrecy found
|
| O | www.mail.ab-polymerchemie.de / 85.16.68.178 / 25
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 8 Cipher Suites without Forward Secrecy found
|
| O | www.mail.ab-polymerchemie.de / 85.16.68.178 / 443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found
|
| O | www.mail.ab-polymerchemie.de / 85.16.68.178 / 465
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 8 Cipher Suites without Forward Secrecy found
|
| O | www.mail.ab-polymerchemie.de / 85.16.68.178 / 587
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 8 Cipher Suites without Forward Secrecy found
|
| X | Fatal error: Nameserver doesn't support TCP connection: l.de.net: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
|
| 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 www.mail.ab-polymerchemie.de, 1 ip addresses, 1 different http results.
|
| 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 mail.ab-polymerchemie.de, 1 ip addresses.
|
| B | No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.mail.ab-polymerchemie.de
|
| 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:: 17 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 17 Queries complete, 17 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 4.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: nsa9.schlundtech.de, nsb9.schlundtech.de, nsc9.schlundtech.de, nsd9.schlundtech.de, 4 Name Servers included in Delegation: nsa9.schlundtech.de, nsb9.schlundtech.de, nsc9.schlundtech.de, nsd9.schlundtech.de, 4 Name Servers included in 1 Zone definitions: nsa9.schlundtech.de, nsb9.schlundtech.de, nsc9.schlundtech.de, nsd9.schlundtech.de, 1 Name Servers listed in SOA.Primary: nsa9.schlundtech.de.
|
| A | Good: Only one SOA.Primary Name Server found.: nsa9.schlundtech.de.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: nsa9.schlundtech.de.
|
| A | Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: nsa9.schlundtech.de, nsb9.schlundtech.de, nsc9.schlundtech.de, nsd9.schlundtech.de
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| A | Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
|
| A | Good: All Name Server ip addresses are public.
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
|
| A | Good: Some Name Servers have IPv6 addresses: 3 Name Servers with IPv6 found (1 Name Servers without IPv6)
|
| 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.: 4 Name Servers, 1 Top Level Domain: de
|
| 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: schlundtech.de
|
| A | Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: DE, US
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 4 different subnets (first Byte): 217., 62., 74., 89., 4 different subnets (first two Bytes): 217.160., 62.116., 74.208., 89.146., 4 different subnets (first three Bytes): 217.160.113., 62.116.159., 74.208.254., 89.146.248.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 3 different subnets (first block): 2001:, 2607:, 2a01:, 3 different subnets (first two blocks): 2001:08d8:, 2607:f1c0:, 2a01:0130:, 3 different subnets (first three blocks): 2001:08d8:0580:, 2607:f1c0:1800:, 2a01:0130:2000:, 3 different subnets (first four blocks): 2001:08d8:0580:0401:, 2607:f1c0:1800:8091:, 2a01:0130:2000:0118:
|
| A | Excellent: Every Name Server IPv6-address starts with an unique Hex-block
|
| A | Good: Nameserver supports TCP connections: 1 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 1 good Nameserver
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: nsa9.schlundtech.de
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: nsb9.schlundtech.de
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: nsc9.schlundtech.de
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: nsd9.schlundtech.de
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
|
| A | Good: All SOA have the same Serial Number
|
| Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
|
| 4. Content- and Performance-critical Checks |
| http://mail.ab-polymerchemie.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.16.68.178
|
| 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.
|
| http://www.mail.ab-polymerchemie.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.16.68.178
|
| 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 | 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: 1009287 milliseconds, 1009.287 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)