| 1. General Results, most used to calculate the result |
| A | name "dmm.co.jp" is domain, public suffix is ".co.jp", top-level-domain is ".jp", top-level-domain-type is "country-code", Country is Japan, tld-manager is "Japan Registry Services Co., Ltd.", num .jp-domains preloaded: 1371 (complete: 263653)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: dmm.co.jp has only one ip address.
|
| Warning: Only one ip address found: www.dmm.co.jp 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: dmm.co.jp 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.dmm.co.jp has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://www.dmm.co.jp/top/
| https://www.dmm.co.jp/age_check/=/?rurl=https%3A%2F%2Fwww.dmm.co.jp%2Ftop%2F
| Correct redirect https to https
|
| A | https://www.dmm.co.jp/age_check/=/?rurl=https%3A%2F%2Fwww.dmm.co.jp%2Ftop%2F
| https://www.dmm.co.jp/en/age_check/=/?rurl=https%3A%2F%2Fwww.dmm.co.jp%2Ftop%2F
| Correct redirect https to https
|
| A | https://www.dmm.co.jp/ 18.64.78.67
| https://www.dmm.co.jp/top/
| Correct redirect https to https
|
| A | Good: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: www is preferred
|
| A | Good: every cookie sent via https is marked as secure
|
| 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):1 complete Content-Type - header (4 urls)
|
| http://www.dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.78.67
|
| Url with incomplete Content-Type - header - missing charset
|
| https://13.248.196.236/ 13.248.196.236
|
| Url with incomplete Content-Type - header - missing charset
|
| https://18.64.78.67/ 18.64.78.67
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://dmm.co.jp/ 13.248.196.236
|
| Missing HSTS-Header
|
| B | https://www.dmm.co.jp/top/
|
| Missing HSTS-Header
|
| B | https://www.dmm.co.jp/age_check/=/?rurl=https%3A%2F%2Fwww.dmm.co.jp%2Ftop%2F
|
| Missing HSTS-Header
|
| B | https://www.dmm.co.jp/ 18.64.78.67
|
| Missing HSTS-Header
|
| B | https://www.dmm.co.jp/en/age_check/=/?rurl=https%3A%2F%2Fwww.dmm.co.jp%2Ftop%2F
|
| Missing HSTS-Header
|
| http://www.dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.78.67
| ckcy=deleted; expires=Sun, 07-Jan-2024 06:10:25 GMT; path=/; domain=.dmm.co.jp
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.78.67
| ckcy=2; expires=Tue, 06-Jan-2026 06:10:26 GMT; path=/; domain=.dmm.co.jp
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.78.67
| althash=deleted; expires=Sun, 07-Jan-2024 06:10:25 GMT; path=/; domain=.dmm.co.jp; secure; httponly
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.78.67
| has_althash=deleted; expires=Sun, 07-Jan-2024 06:10:25 GMT; path=/; domain=.dmm.co.jp; httponly
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| B | https://www.dmm.co.jp/top/
| top_pv_uid=246962a7-9a08-413a-b8aa-a70853effc68; Domain=.dmm.co.jp; Max-Age=31536000; Path=/; Secure
| 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.dmm.co.jp/top/
| top_dummy=30250b7b-9eaa-4fb7-a193-5a72f11fd571; Domain=.dmm.co.jp; Max-Age=31536000; Path=/; Secure
| 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 | http://www.dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.78.67
| ckcy=deleted; expires=Sun, 07-Jan-2024 06:10:25 GMT; path=/; domain=.dmm.co.jp
| 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 | http://www.dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.78.67
| ckcy=2; expires=Tue, 06-Jan-2026 06:10:26 GMT; path=/; domain=.dmm.co.jp
| 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 | http://www.dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.78.67
| althash=deleted; expires=Sun, 07-Jan-2024 06:10:25 GMT; path=/; domain=.dmm.co.jp; secure; httponly
| 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 | http://www.dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.78.67
| has_althash=deleted; expires=Sun, 07-Jan-2024 06:10:25 GMT; path=/; domain=.dmm.co.jp; httponly
| 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.
|
| D | http://dmm.co.jp/ 13.248.196.236
| http://www.dmm.co.jp/
| 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.dmm.co.jp/ 18.64.78.67
| http://www.dmm.co.jp/top/
| 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://dmm.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.196.236
| http://www.dmm.co.jp/.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://13.248.196.236/ 13.248.196.236
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://18.64.78.67/ 18.64.78.67
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://13.248.196.236/ 13.248.196.236
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://18.64.78.67/ 18.64.78.67
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 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.dmm.co.jp, 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 dmm.co.jp, 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.dmm.co.jp
|
| 2. Header-Checks |
| F | www.dmm.co.jp
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.dmm.co.jp
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.dmm.co.jp
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.dmm.co.jp
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.dmm.co.jp
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.dmm.co.jp
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.dmm.co.jp
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 28 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 10 Name Servers.
|
| A | Info:: 28 Queries complete, 28 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.a12-67.akam.net (184.26.160.67, 2600:1480:f000::43)
|
| A | Good (1 - 3.0):: An average of 2.8 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: ns-1396.awsdns-46.org, ns-1616.awsdns-10.co.uk, ns-33.awsdns-04.com, ns-742.awsdns-28.net, 4 Name Servers included in Delegation: ns-1396.awsdns-46.org, ns-1616.awsdns-10.co.uk, ns-33.awsdns-04.com, ns-742.awsdns-28.net, 4 Name Servers included in 1 Zone definitions: ns-1396.awsdns-46.org, ns-1616.awsdns-10.co.uk, ns-33.awsdns-04.com, ns-742.awsdns-28.net, 1 Name Servers listed in SOA.Primary: ns-1616.awsdns-10.co.uk.
|
| A | Good: Only one SOA.Primary Name Server found.: ns-1616.awsdns-10.co.uk.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns-1616.awsdns-10.co.uk.
|
| 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: a1-198.akam.net, a12-67.akam.net, a13-64.akam.net, a14-65.akam.net, a18-66.akam.net, a9-67.akam.net, ns1.p201.dns.oraclecloud.net, ns2.p201.dns.oraclecloud.net, ns3.p201.dns.oraclecloud.net, ns4.p201.dns.oraclecloud.net
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 10 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 10 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.: 10 Name Servers, 1 Top Level Domain: net
|
| A | Good: Name Servers with different domain names found.: 2 different Domains found
|
| A | Good: Name servers with different Country locations found: 10 Name Servers, 6 Countries: DE, ES, KR, PL, SA, US
|
| A |
|
| A | Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
|
| A | Good: Nameserver supports TCP connections: 20 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 20 good Nameserver
|
| X | Nameserver Timeout checking EDNS512: a12-67.akam.net / 2600:1480:f000::43
|
| 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.
|
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://www.dmm.co.jp/en/age_check/=/?rurl=https%3A%2F%2Fwww.dmm.co.jp%2Ftop%2F
|
| 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 | 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: 225124 milliseconds, 225.124 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)