| 1. General Results, most used to calculate the result |
| A | name "toaanvinhthanh.gov.vn" is domain, public suffix is "gov.vn", top-level-domain-type is "country-code", Country is Viet Nam, tld-manager is "Ministry of Information and Communications of Socialist Republic of Viet Nam"
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: toaanvinhthanh.gov.vn has only one ip address.
|
| Warning: Only one ip address found: www.toaanvinhthanh.gov.vn 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: toaanvinhthanh.gov.vn 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.toaanvinhthanh.gov.vn has no ipv6 address.
|
| A | Good: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: non-www is preferred
|
| 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (3 urls)
|
| https://103.97.124.238/ 103.97.124.238
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://toaanvinhthanh.gov.vn/ 103.97.124.238
| https://toaanvinhthanh.gov.vn/
| Correct redirect http - https with the same domain name
|
| B | https://www.toaanvinhthanh.gov.vn/ 103.97.124.238
|
| Missing HSTS-Header
|
| B | https://103.97.124.238/ 103.97.124.238
|
| Missing HSTS-Header
|
| B | https://toaanvinhthanh.gov.vn/ 103.97.124.238
| nv4c_a6N7Z_ctr=ODVfMjE1XzJfMjI3LkRF; Path=/; Domain=.toaanvinhthanh.gov.vn; Expires=2021-05-09 11:28:30; HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | https://toaanvinhthanh.gov.vn/ 103.97.124.238
| nv4c_a6N7Z_sess=ge2276qkfaae87iagrdi3ddnko; Path=/; Domain=.toaanvinhthanh.gov.vn; HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | https://toaanvinhthanh.gov.vn/ 103.97.124.238
| nv4c_a6N7Z_statistic_vi=I-EtQwzaQIsk7ULTt1bbUA%2C%2C; Path=/; Domain=.toaanvinhthanh.gov.vn; Expires=2020-05-09 11:58:30; HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | https://toaanvinhthanh.gov.vn/ 103.97.124.238
| nv4c_a6N7Z_nvvithemever=S4EBQj8NVbSuNUTVXdYMpw%2C%2C; Path=/; Domain=.toaanvinhthanh.gov.vn; Expires=2021-05-04 11:28:30; HttpOnly
| Cookie sent via https, but not marked as secure
|
| D | http://www.toaanvinhthanh.gov.vn/ 103.97.124.238
| http://toaanvinhthanh.gov.vn/
| 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.toaanvinhthanh.gov.vn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 103.97.124.238
| http://toaanvinhthanh.gov.vn/.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.
|
| N | https://103.97.124.238/ 103.97.124.238
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 103.97.124.238:2222
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| X | Fatal error: Nameserver doesn't support TCP connection: f.dns-servers.vn / 2001:dc8:d000:2::105: 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 toaanvinhthanh.gov.vn, 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.toaanvinhthanh.gov.vn, 1 ip addresses.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 different Name Servers found: ns1.vinades.vn, ns3.vinades.vn, 2 Name Servers included in Delegation: ns1.vinades.vn, ns3.vinades.vn, 2 Name Servers included in 2 Zone definitions: ns1.vinades.vn, ns3.vinades.vn, 1 Name Servers listed in SOA.Primary: ns1.vinades.vn.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.vinades.vn.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.vinades.vn.
|
| 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: vn
|
| 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: vinades.vn
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: VN
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 112., 222., 2 different subnets (first two Bytes): 112.213., 222.255., 2 different subnets (first three Bytes): 112.213.89., 222.255.121.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: ns3.vinades.vn / 112.213.89.22
|
| X | Nameserver Timeout checking EDNS512: ns3.vinades.vn / 112.213.89.22
|
| Nameserver doesn't pass all EDNS-Checks: a.dns-servers.vn / 194.0.1.18: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: c.dns-servers.vn / 2001:dc8:c000:7::105: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: dns-master.vnnic.vn: 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: dns-master.vnnic.vn: 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: e.dns-servers.vn / 203.119.60.105: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: e.dns-servers.vn / 2001:dc8:1000:2::105: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: f.dns-servers.vn / 2001:dc8:d000:2::105: OP100: fatal timeout. FLAGS: fatal timeout. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns3.vinades.vn / 112.213.89.22: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. 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.
|
| https://toaanvinhthanh.gov.vn/ 103.97.124.238
|
| 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://toaanvinhthanh.gov.vn/ 103.97.124.238
|
| 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://toaanvinhthanh.gov.vn/ 103.97.124.238
|
| 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.
|
| https://103.97.124.238/ 103.97.124.238
|
| 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.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 24 external CSS / JavaScript files found
|
| Warning: Images with internal compression and Compression found. Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so additional Compression isn't helpful. Don't send these images with gzip/deflate/br. 1 images (type image/png, image/jpg) found with additional GZip. GZip is not required, these images are already compressed. 7 images (type image/png, image/jpg) without GZip found. 8 images (type image/png, image/jpg) complete.
|
| A | Good: All CSS / JavaScript files are sent with a long Cache-Control header (minimum 7 days). So the browser can re-use these files, no download is required. 24 external CSS / JavaScript files with long Cache-Control max-age found
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 image files without Cache-Control-Header, 1 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 43 with Cache-Control long enough, 44 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: Some img-elements have a valid alt-attribute.: 44 img-elements found, 42 img-elements with correct alt-attributes (defined, not an empty value).
|
| 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.: 2 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
|
| A | Duration: 561604 milliseconds, 561.604 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)