| 1. General Results, most used to calculate the result |
| A | name "softwarelabs.id" is domain, public suffix is "id", top-level-domain-type is "country-code", Country is Indonesia, tld-manager is "Perkumpulan Pengelola Nama Domain Internet Indonesia (PANDI)"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
|
| 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: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| A | Good: HSTS has includeSubdomains - directive
|
| 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.
|
| 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| A | http://softwarelabs.id/ 178.128.110.174
| https://softwarelabs.id/
| Correct redirect http - https with the same domain name
|
| X | Fatal error: Nameserver doesn't support TCP connection: dns4.masterwebnet.com / 202.78.200.59: Timeout
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns1.masterwebnet.com (202.157.177.169): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns2.masterweb.net (45.64.1.209): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns3.masterweb.com (149.28.149.165): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns3.masterwebnet.com (149.28.149.165): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns4.masterweb.net (45.79.30.92): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns1.masterweb.com (202.157.177.169): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net
|
| A | Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
|
| X | Nameserver Timeout checking Echo Capitalization: dns4.masterwebnet.com / 202.78.200.59
|
| X | Nameserver Timeout checking EDNS512: dns4.masterwebnet.com / 202.78.200.59
|
| Nameserver doesn't pass all EDNS-Checks: dns1.masterweb.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
|
| Nameserver doesn't pass all EDNS-Checks: dns4.masterwebnet.com / 202.78.200.59: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns4.apnic.net: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns4-de1.apnic.net). COOKIE: fatal timeout. 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.
|
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://softwarelabs.id/ 178.128.110.174
|
| 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://softwarelabs.id/ 178.128.110.174
|
| 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://softwarelabs.id/ 178.128.110.174
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| 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: 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
|
| http://softwarelabs.id/ 178.128.110.174
|
| Warning: HSTS header sent via http has no effect
|
| https://softwarelabs.id/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 4.577 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 135310 milliseconds, 135.310 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)