| 1. General Results, most used to calculate the result |
| A | name "premium-security.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 108094 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: premium-security.com has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.premium-security.com has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: premium-security.com has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.premium-security.com has 1 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://premium-security.com/ 95.216.251.165
|
| Good: Valid DANE - entry found: signed Data _443._tcp.premium-security.com: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 389be9b36d679ebf4483697fa4f100d0cb775fb9ef0c37d5eb2b36bf963c217a confirms the Certificate with the same value
|
| A | https://premium-security.com/ 2a01:4f9:1a:3a01::110
|
| Good: Valid DANE - entry found: signed Data _443._tcp.premium-security.com: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 389be9b36d679ebf4483697fa4f100d0cb775fb9ef0c37d5eb2b36bf963c217a confirms the Certificate with the same value
|
| A | https://premium-security.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Good: Valid DANE - entry found: signed Data _443._tcp.premium-security.com: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 389be9b36d679ebf4483697fa4f100d0cb775fb9ef0c37d5eb2b36bf963c217a confirms the Certificate with the same value
|
| A | https://95.216.251.165/ 95.216.251.165
|
| Good: Valid DANE - entry found: signed Data _443._tcp.premium-security.com: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 389be9b36d679ebf4483697fa4f100d0cb775fb9ef0c37d5eb2b36bf963c217a confirms the Certificate with the same value
|
| A | https://[2a01:04f9:001a:3a01:0000:0000:0000:0110]/ 2a01:4f9:1a:3a01::110
|
| Good: Valid DANE - entry found: signed Data _443._tcp.premium-security.com: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 389be9b36d679ebf4483697fa4f100d0cb775fb9ef0c37d5eb2b36bf963c217a confirms the Certificate with the same value
|
| A | https://mta-sts.premium-security.com/.well-known/mta-sts.txt 95.216.251.165
|
| Good: Valid DANE - entry found: signed Data _443._tcp.premium-security.com: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 389be9b36d679ebf4483697fa4f100d0cb775fb9ef0c37d5eb2b36bf963c217a confirms the Certificate with the same value
|
| A | https://mta-sts.premium-security.com/.well-known/mta-sts.txt 2a01:4f9:1a:3a01::110
|
| Good: Valid DANE - entry found: signed Data _443._tcp.premium-security.com: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 389be9b36d679ebf4483697fa4f100d0cb775fb9ef0c37d5eb2b36bf963c217a confirms the Certificate with the same value
|
| A | Good: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: non-www is preferred
|
| A | Good: No cookie sent via http.
|
| A | Good: HSTS has preload directive
|
| Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
|
| A |
|
| HSTS-Preload-Status: Pending. Submission of the domain successful, domain is pending. 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):3 complete Content-Type - header (5 urls)
|
| https://mta-sts.premium-security.com/.well-known/mta-sts.txt 95.216.251.165
|
| Url with incomplete Content-Type - header - missing charset
|
| https://mta-sts.premium-security.com/.well-known/mta-sts.txt 2a01:4f9:1a:3a01::110
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://premium-security.com/ 95.216.251.165
| https://premium-security.com/
| Correct redirect http - https with the same domain name
|
| A | http://premium-security.com/ 2a01:4f9:1a:3a01::110
| https://premium-security.com/
| Correct redirect http - https with the same domain name
|
| A | http://www.premium-security.com/ 95.216.251.165
| https://www.premium-security.com/
| Correct redirect http - https with the same domain name
|
| A | http://www.premium-security.com/ 2a01:4f9:1a:3a01::110
| https://www.premium-security.com/
| Correct redirect http - https with the same domain name
|
| 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 premium-security.com, 2 ip addresses.
|
| 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 www.premium-security.com, 2 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain premium-security.com, 2 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.premium-security.com, 2 ip addresses.
|
| A | Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.premium-security.com
|
| A | Good: _mta-sts TXT record is valid.
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.premium-security.com, ip : 95.216.251.165
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.premium-security.com, ip : 2a01:4f9:1a:3a01::110
|
| A | Good: Certificate of subdomain is valid. mta-sts.premium-security.com, ip : 95.216.251.165
|
| A | Good: Certificate of subdomain is valid. mta-sts.premium-security.com, ip : 2a01:4f9:1a:3a01::110
|
| A | Good: /.well-known/mta-sts.txt with http status 200 found. Complete path: https://mta-sts.premium-security.com/.well-known/mta-sts.txt - ip : 95.216.251.165
|
| A | Good: /.well-known/mta-sts.txt with http status 200 found. Complete path: https://mta-sts.premium-security.com/.well-known/mta-sts.txt - ip : 2a01:4f9:1a:3a01::110
|
| A | Good: mta-sts.txt has the required names "version", "mode", "max_age". mta-sts.premium-security.com, ip : 95.216.251.165
|
| A | Good: mta-sts.txt has the required names "version", "mode", "max_age". mta-sts.premium-security.com, ip : 2a01:4f9:1a:3a01::110
|
| A | Good: Minimal one mx definition found. mta-sts.premium-security.com, ip : 95.216.251.165
|
| A | Good: Minimal one mx definition found. mta-sts.premium-security.com, ip : 2a01:4f9:1a:3a01::110
|
| A | Excellent: Complete and valid MTA-STS found!
|
| 2. Header-Checks |
| A | premium-security.com 95.216.251.165
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; frame-src 'self'; object-src 'none'; img-src 'self' data:; style-src 'self'; script-src 'self'; font-src 'self' data:; connect-src 'self'; upgrade-insecure-requests
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked. connect-src, frame-src, script-src, style-src
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'. connect-src, frame-src, script-src, style-src
|
| A |
|
| Good: form-action directive found. That reduces the risk sending data to unwanted domains. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: base-uri directive found. That limits the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| A |
|
| Good: script-src without 'unsafe-inline' and 'unsafe-eval' found. That's the recommended configuration.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| C |
|
| Info: default-src and some other fetch directives have the same list of values. Remove the other fetch directive, default-src is used as fallback. Directives to remove: connect-src, frame-src, script-src, style-src
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: same-origin
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| A | premium-security.com 2a01:4f9:1a:3a01::110
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; frame-src 'self'; object-src 'none'; img-src 'self' data:; style-src 'self'; script-src 'self'; font-src 'self' data:; connect-src 'self'; upgrade-insecure-requests
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked. connect-src, frame-src, script-src, style-src
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'. connect-src, frame-src, script-src, style-src
|
| A |
|
| Good: form-action directive found. That reduces the risk sending data to unwanted domains. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: base-uri directive found. That limits the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| A |
|
| Good: script-src without 'unsafe-inline' and 'unsafe-eval' found. That's the recommended configuration.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| C |
|
| Info: default-src and some other fetch directives have the same list of values. Remove the other fetch directive, default-src is used as fallback. Directives to remove: connect-src, frame-src, script-src, style-src
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: same-origin
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| F | premium-security.com 95.216.251.165
| Permissions-Policy
| Critical: Missing Header:
|
| B | premium-security.com 95.216.251.165
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | premium-security.com 95.216.251.165
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | premium-security.com 95.216.251.165
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | premium-security.com 2a01:4f9:1a:3a01::110
| Permissions-Policy
| Critical: Missing Header:
|
| B | premium-security.com 2a01:4f9:1a:3a01::110
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | premium-security.com 2a01:4f9:1a:3a01::110
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | premium-security.com 2a01:4f9:1a:3a01::110
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| A | Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns0.premium-security.com (2a01:4f9:1a:3a01::50, 95.216.251.165), ns1.premium-security.com (2600:1f14:2913:dcf1:1895:7e43:200c:ff8c, 50.112.130.136)
|
| A | Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns0.premium-security.com, ns1.premium-security.com, 2 Name Servers included in Delegation: ns0.premium-security.com, ns1.premium-security.com, 2 Name Servers included in 1 Zone definitions: ns0.premium-security.com, ns1.premium-security.com, 1 Name Servers listed in SOA.Primary: ns0.premium-security.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns0.premium-security.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns0.premium-security.com.
|
| 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: ns0.premium-security.com, ns1.premium-security.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 | Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
|
| A | Good: 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: com
|
| 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: premium-security.com
|
| A | Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: FI, US
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 50., 95., 2 different subnets (first two Bytes): 50.112., 95.216., 2 different subnets (first three Bytes): 50.112.130., 95.216.251.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 2 different subnets (first block): 2600:, 2a01:, 2 different subnets (first two blocks): 2600:1f14:, 2a01:04f9:, 2 different subnets (first three blocks): 2600:1f14:2913:, 2a01:04f9:001a:, 2 different subnets (first four blocks): 2600:1f14:2913:dcf1:, 2a01:04f9:001a:3a01:
|
| A | Excellent: Every Name Server IPv6-address starts with an unique Hex-block
|
| 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): 4 good Nameserver
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: no CAA is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create wildcard-certificates
|
| 4. Content- and Performance-critical Checks |
| A | Good: 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.
|
| https://premium-security.com/ 95.216.251.165
|
| 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://premium-security.com/ 2a01:4f9:1a:3a01::110
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| A | Good: All images with internal compression not compressed. Some Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so an additional compression isn't helpful. 2 images (type image/png, image/jpg, image/jpeg, image/webp, image/gif) found without additional Compression. Not required because these images are already compressed
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 2 img-elements without alt-attribute, 0 img-elements with empty alt-attribute found.
|
| 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
|
| https://premium-security.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.346 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 349384 milliseconds, 349.384 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)