| 1. General Results, most used to calculate the result |
| A | name "embedcover.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: 103088 (complete: 263653)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: embedcover.com has 2 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: embedcover.com has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: No cookie sent via http.
|
| A | Good: every cookie sent via https is marked as secure
|
| A | Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None
|
| HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
|
| https://embedcover.com/ 75.2.70.75
|
| Url with incomplete Content-Type - header - missing charset
|
| https://embedcover.com/ 99.83.190.102
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.embedcover.com/ 18.102.16.191
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.embedcover.com/ 35.152.104.113
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.embedcover.com/ 35.152.119.144
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://embedcover.com/ 75.2.70.75
| https://embedcover.com/
| Correct redirect http - https with the same domain name
|
| A | http://embedcover.com/ 99.83.190.102
| https://embedcover.com/
| Correct redirect http - https with the same domain name
|
| A | http://www.embedcover.com/ 18.102.16.191
| https://www.embedcover.com/
| Correct redirect http - https with the same domain name
|
| A | http://www.embedcover.com/ 35.152.104.113
| https://www.embedcover.com/
| Correct redirect http - https with the same domain name
|
| A | http://www.embedcover.com/ 35.152.119.144
| https://www.embedcover.com/
| Correct redirect http - https with the same domain name
|
| B | https://embedcover.com/ 75.2.70.75
|
| Missing HSTS-Header
|
| B | https://embedcover.com/ 99.83.190.102
|
| Missing HSTS-Header
|
| B | https://www.embedcover.com/ 18.102.16.191
|
| Missing HSTS-Header
|
| B | https://www.embedcover.com/ 35.152.104.113
|
| Missing HSTS-Header
|
| B | https://www.embedcover.com/ 35.152.119.144
|
| Missing HSTS-Header
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| M | https://embedcover.com/ 75.2.70.75
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://embedcover.com/ 99.83.190.102
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://www.embedcover.com/ 18.102.16.191
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://www.embedcover.com/ 35.152.104.113
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://www.embedcover.com/ 35.152.119.144
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| 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 embedcover.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 embedcover.com, 2 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.embedcover.com
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| F | embedcover.com 75.2.70.75
| Content-Security-Policy
| Critical: Missing Header:
|
| F | embedcover.com 75.2.70.75
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | embedcover.com 75.2.70.75
| Referrer-Policy
| Critical: Missing Header:
|
| F | embedcover.com 75.2.70.75
| Permissions-Policy
| Critical: Missing Header:
|
| B | embedcover.com 75.2.70.75
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | embedcover.com 75.2.70.75
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | embedcover.com 75.2.70.75
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | embedcover.com 99.83.190.102
| Content-Security-Policy
| Critical: Missing Header:
|
| F | embedcover.com 99.83.190.102
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | embedcover.com 99.83.190.102
| Referrer-Policy
| Critical: Missing Header:
|
| F | embedcover.com 99.83.190.102
| Permissions-Policy
| Critical: Missing Header:
|
| B | embedcover.com 99.83.190.102
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | embedcover.com 99.83.190.102
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | embedcover.com 99.83.190.102
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.embedcover.com 18.102.16.191
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.embedcover.com 18.102.16.191
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.embedcover.com 18.102.16.191
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.embedcover.com 18.102.16.191
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.embedcover.com 18.102.16.191
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.embedcover.com 18.102.16.191
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.embedcover.com 18.102.16.191
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.embedcover.com 35.152.104.113
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.embedcover.com 35.152.104.113
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.embedcover.com 35.152.104.113
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.embedcover.com 35.152.104.113
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.embedcover.com 35.152.104.113
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.embedcover.com 35.152.104.113
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.embedcover.com 35.152.104.113
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.embedcover.com 35.152.119.144
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.embedcover.com 35.152.119.144
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.embedcover.com 35.152.119.144
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.embedcover.com 35.152.119.144
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.embedcover.com 35.152.119.144
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.embedcover.com 35.152.119.144
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.embedcover.com 35.152.119.144
| 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.dns200.anycast.me (46.105.206.200), ns200.anycast.me (46.105.207.200)
|
| 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: dns200.anycast.me, ns200.anycast.me, 2 Name Servers included in Delegation: dns200.anycast.me, ns200.anycast.me, 2 Name Servers included in 1 Zone definitions: dns200.anycast.me, ns200.anycast.me, 1 Name Servers listed in SOA.Primary: dns200.anycast.me.
|
| A | Good: Only one SOA.Primary Name Server found.: dns200.anycast.me.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: dns200.anycast.me.
|
| 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: dns200.anycast.me, ns200.anycast.me
|
| 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
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 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: me
|
| 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: anycast.me
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 46., 1 different subnets (first two Bytes): 46.105., 2 different subnets (first three Bytes): 46.105.206., 46.105.207.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 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://embedcover.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 75.2.70.75
|
| 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://embedcover.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 99.83.190.102
|
| 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.embedcover.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.102.16.191
|
| 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.embedcover.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 35.152.104.113
|
| 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.embedcover.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 35.152.119.144
|
| 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: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 3 external CSS / JavaScript files found
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 3 external CSS / JavaScript 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, 3 complete.
|
| 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
|
| https://www.embedcover.com/ 18.102.16.191
| 3.200 seconds
| Warning: 404 needs more then one second
|
| https://www.embedcover.com/ 35.152.104.113
| 3.007 seconds
| Warning: 404 needs more then one second
|
| https://www.embedcover.com/ 35.152.119.144
| 2.770 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 234480 milliseconds, 234.480 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)