| 1. General Results, most used to calculate the result |
| A | name "amplify.app" is domain, public suffix is ".app", top-level-domain is ".app", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .app-domains preloaded: 47 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: amplify.app has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.amplify.app 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: amplify.app 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.amplify.app has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://www.amplify.app/ 207.207.210.36
| https://www.godaddy.com/forsale/amplify.app
| Correct redirect https to https
|
| A | https://www.amplify.app/ 207.207.210.50
| https://www.godaddy.com/forsale/amplify.app
| Correct redirect https to https
|
| A | Good: No cookie sent via http.
|
| A | Excellent: Domain is in the Google-Preload-List
|
| A | Excellent: Domain is in the Mozilla/Firefox-Preload-List
|
| A | HSTS-Preload-Status: Preloaded. 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 (1 urls)
|
| https://www.godaddy.com/forsale/amplify.app
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://amplify.app/ 207.207.210.36
|
| Missing HSTS-Header
|
| B | https://amplify.app/ 207.207.210.50
|
| Missing HSTS-Header
|
| B | https://www.amplify.app/ 207.207.210.36
|
| Missing HSTS-Header
|
| B | https://www.amplify.app/ 207.207.210.50
|
| Missing HSTS-Header
|
| B | https://www.godaddy.com/forsale/amplify.app
|
| Missing HSTS-Header
|
| B | https://www.godaddy.com/forsale/amplify.app
| market=de-DE; expires=Thu, 19-Aug-2027 15:07:14 GMT; path=/; domain=.godaddy.com
| Cookie sent via https, but not marked as secure
|
| B | https://www.godaddy.com/forsale/amplify.app
| currency=EUR; expires=Thu, 19-Aug-2027 15:07:14 GMT; path=/; domain=.godaddy.com
| Cookie sent via https, but not marked as secure
|
| B | https://www.godaddy.com/forsale/amplify.app
| market=de-DE; expires=Thu, 19-Aug-2027 15:07:14 GMT; path=/; domain=.godaddy.com
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://www.godaddy.com/forsale/amplify.app
| currency=EUR; expires=Thu, 19-Aug-2027 15:07:14 GMT; path=/; domain=.godaddy.com
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| C | Error - no version with Http-Status 200
|
| E | http://amplify.app/ 207.207.210.36
| https://www.godaddy.com/forsale/amplify.app
| 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://amplify.app/ 207.207.210.50
| https://www.godaddy.com/forsale/amplify.app
| 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://www.amplify.app/ 207.207.210.36
| https://www.godaddy.com/forsale/amplify.app
| 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://www.amplify.app/ 207.207.210.50
| https://www.godaddy.com/forsale/amplify.app
| 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
|
| K | http://amplify.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 207.207.210.36, Status -14
| http://amplify.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 207.207.210.50, Status 302
| Configuration problem - different ip addresses with different status
|
| M | https://www.godaddy.com/forsale/amplify.app
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain amplify.app, 2 ip addresses, 2 different http results.
|
| Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain www.amplify.app, 2 ip addresses, 2 different http results.
|
| 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 amplify.app, 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.amplify.app, 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.amplify.app
|
| 2. Header-Checks |
| A | www.godaddy.com
| X-Frame-Options
| Ok: Header without syntax errors found: DENY
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. DENY. 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 | www.godaddy.com
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.godaddy.com
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.godaddy.com
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.godaddy.com
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.godaddy.com
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.godaddy.com
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.godaddy.com
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 25 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
|
| A | Info:: 25 Queries complete, 25 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| A | Info:: 4 different Name Servers found: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com, 4 Name Servers included in Delegation: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com, 4 Name Servers included in 1 Zone definitions: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com, 1 Name Servers listed in SOA.Primary: curitiba.ns.porkbun.com.
|
| A | Good: Only one SOA.Primary Name Server found.: curitiba.ns.porkbun.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: curitiba.ns.porkbun.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: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.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: 4 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: porkbun.com
|
| A | Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: CA, US
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 2 different subnets (first Byte): 162., 173., 2 different subnets (first two Bytes): 162.159., 173.245., 4 different subnets (first three Bytes): 162.159.10., 162.159.11., 162.159.8., 173.245.58.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2400:, 1 different subnets (first two blocks): 2400:cb00:, 1 different subnets (first three blocks): 2400:cb00:2049:, 1 different subnets (first four blocks): 2400:cb00:2049:0001:
|
| Fatal: All Name Server IPv6 addresses from the same subnet.
|
| A | Good: Nameserver supports TCP connections: 8 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 8 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: amazon.com is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: godaddy.com is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: wordpress.com is allowed to create wildcard-certificates
|
| Warning: Unknown CAA found: wordpress.com isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| 4. Content- and Performance-critical Checks |
| http://amplify.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 207.207.210.36
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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 | Info: Different Server-Headers found
|
| A | Duration: 775364 milliseconds, 775.364 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)