| 1. General Results, most used to calculate the result |
| A | name "fionaandsam.wedding" is domain, public suffix is ".wedding", top-level-domain is ".wedding", top-level-domain-type is "generic", tld-manager is "Minds + Machines Group Limited", num .wedding-domains preloaded: 37 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: fionaandsam.wedding has only one ip address.
|
| Warning: Only one ip address found: www.fionaandsam.wedding 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: fionaandsam.wedding 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.fionaandsam.wedding has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| 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.
|
| 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 (3 urls)
|
| https://fionaandsam.wedding/ 159.223.246.32
|
| Url with incomplete Content-Type - header - missing charset
|
| https://fionaandsam.wedding/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://159.223.246.32/ 159.223.246.32
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://fionaandsam.wedding/ 159.223.246.32
| https://fionaandsam.wedding/
| Correct redirect http - https with the same domain name
|
| B | https://www.fionaandsam.wedding/ 159.223.246.32
|
| Missing HSTS-Header
|
| D | http://www.fionaandsam.wedding/ 159.223.246.32
| http://fionaandsam.wedding/
| 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.fionaandsam.wedding/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 159.223.246.32
| http://fionaandsam.wedding/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 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.
|
| M | https://159.223.246.32/ 159.223.246.32
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://159.223.246.32/ 159.223.246.32
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| X | Fatal error: Nameserver doesn't support TCP connection: y.nic.wedding: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: z.nic.wedding: Timeout
|
| 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 fionaandsam.wedding, 1 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain www.fionaandsam.wedding, 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.fionaandsam.wedding
|
| 2. Header-Checks |
| F | fionaandsam.wedding 159.223.246.32
| Content-Security-Policy
| Critical: Missing Header:
|
| F | fionaandsam.wedding 159.223.246.32
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | fionaandsam.wedding 159.223.246.32
| Referrer-Policy
| Critical: Missing Header:
|
| F | fionaandsam.wedding 159.223.246.32
| Permissions-Policy
| Critical: Missing Header:
|
| B | fionaandsam.wedding 159.223.246.32
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | fionaandsam.wedding 159.223.246.32
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | fionaandsam.wedding 159.223.246.32
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 10 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 10 Queries complete, 10 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 3 Name Servers included in Delegation: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 3 Name Servers included in 1 Zone definitions: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 1 Name Servers listed in SOA.Primary: ns1.digitalocean.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.digitalocean.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.digitalocean.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: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.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: 3 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 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: digitalocean.com
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: CA
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 1 different subnets (first Byte): 172., 1 different subnets (first two Bytes): 172.64., 3 different subnets (first three Bytes): 172.64.49., 172.64.52., 172.64.53.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2606:, 1 different subnets (first two blocks): 2606:4700:, 2 different subnets (first three blocks): 2606:4700:0052:, 2606:4700:005a:, 2 different subnets (first four blocks): 2606:4700:0052:0000:, 2606:4700:005a:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 6 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 6 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: a.nic.wedding
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
|
| X | Nameserver Timeout checking EDNS512: c.nic.wedding
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: a.nic.wedding: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (dns4.defra1). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: c.nic.wedding: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (dns4.defra1). 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 |
| 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://fionaandsam.wedding/ 159.223.246.32
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://fionaandsam.wedding/ 159.223.246.32
|
| Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
|
| https://fionaandsam.wedding/ 159.223.246.32
|
| 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 CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 1 external CSS / JavaScript files found
|
| 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. 1 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: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 3 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 3 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 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, 1 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.: 1 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://fionaandsam.wedding/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.343 seconds
| Warning: 404 needs more then one second
|
| https://159.223.246.32/ 159.223.246.32
| 2.317 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 184337 milliseconds, 184.337 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)