| 1. General Results, most used to calculate the result |
| A | name "mytel.com.mm" is domain, public suffix is ".*.mm", top-level-domain is ".mm", top-level-domain-type is "country-code", Country is Myanmar, tld-manager is "Ministry of Transport and Communications", num .mm-domains preloaded: 1 (complete: 231048)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: mytel.com.mm has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.mytel.com.mm 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: mytel.com.mm 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.mytel.com.mm has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: one preferred version: 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 (14 urls)
|
| http://mytel.com.mm/ 202.191.109.42
|
| Url with incomplete Content-Type - header - missing charset
|
| http://mytel.com.mm/ 202.191.109.43
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.mytel.com.mm/ 202.191.109.42
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.mytel.com.mm/ 202.191.109.43
|
| Url with incomplete Content-Type - header - missing charset
|
| https://mytel.com.mm/ 202.191.109.42
|
| Url with incomplete Content-Type - header - missing charset
|
| https://mytel.com.mm/ 202.191.109.43
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.mytel.com.mm/ 202.191.109.42
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.mytel.com.mm/ 202.191.109.43
|
| Url with incomplete Content-Type - header - missing charset
|
| http://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.191.109.42
|
| Url with incomplete Content-Type - header - missing charset
|
| http://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.191.109.43
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.191.109.42
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.191.109.43
|
| Url with incomplete Content-Type - header - missing charset
|
| https://202.191.109.42/ 202.191.109.42
|
| Url with incomplete Content-Type - header - missing charset
|
| https://202.191.109.43/ 202.191.109.43
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://mytel.com.mm/ 202.191.109.42
|
| Missing HSTS-Header
|
| B | https://mytel.com.mm/ 202.191.109.43
|
| Missing HSTS-Header
|
| B | https://www.mytel.com.mm/ 202.191.109.42
|
| Missing HSTS-Header
|
| B | https://www.mytel.com.mm/ 202.191.109.43
|
| Missing HSTS-Header
|
| H | Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. 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.
|
| M | http://mytel.com.mm/ 202.191.109.42
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | http://mytel.com.mm/ 202.191.109.43
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://mytel.com.mm/ 202.191.109.42
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://mytel.com.mm/ 202.191.109.43
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://202.191.109.42/ 202.191.109.42
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://202.191.109.43/ 202.191.109.43
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain mytel.com.mm, 2 ip addresses.
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.mytel.com.mm, 2 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 mytel.com.mm, 2 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.mytel.com.mm, 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.mytel.com.mm
|
| 2. Header-Checks |
| F | mytel.com.mm 202.191.109.42
| Content-Security-Policy
| Critical: Missing Header:
|
| F | mytel.com.mm 202.191.109.42
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | mytel.com.mm 202.191.109.42
| Referrer-Policy
| Critical: Missing Header:
|
| F | mytel.com.mm 202.191.109.42
| Permissions-Policy
| Critical: Missing Header:
|
| F | mytel.com.mm 202.191.109.43
| Content-Security-Policy
| Critical: Missing Header:
|
| F | mytel.com.mm 202.191.109.43
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | mytel.com.mm 202.191.109.43
| Referrer-Policy
| Critical: Missing Header:
|
| F | mytel.com.mm 202.191.109.43
| Permissions-Policy
| Critical: Missing Header:
|
| F | www.mytel.com.mm 202.191.109.42
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.mytel.com.mm 202.191.109.42
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.mytel.com.mm 202.191.109.42
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.mytel.com.mm 202.191.109.42
| Permissions-Policy
| Critical: Missing Header:
|
| F | www.mytel.com.mm 202.191.109.43
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.mytel.com.mm 202.191.109.43
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.mytel.com.mm 202.191.109.43
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.mytel.com.mm 202.191.109.43
| Permissions-Policy
| Critical: Missing Header:
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 2 Queries complete, 1 with IPv6, 1 with IPv4.
|
| Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
|
| 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.ns1.mtalk.net.mm (103.47.185.210), ns2.mtalk.net.mm (202.157.134.58)
|
| A | Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.mtalk.net.mm, ns2.mtalk.net.mm, 2 Name Servers included in Delegation: ns1.mtalk.net.mm, ns2.mtalk.net.mm, 2 Name Servers included in 1 Zone definitions: ns1.mtalk.net.mm, ns2.mtalk.net.mm, 1 Name Servers listed in SOA.Primary: ns1.mtalk.net.mm.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.mtalk.net.mm.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.mtalk.net.mm.
|
| 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.mtalk.net.mm, ns2.mtalk.net.mm
|
| 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: *.mm
|
| 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: net.mm
|
| A | Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: MM, SG
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 103., 202., 2 different subnets (first two Bytes): 103.47., 202.157., 2 different subnets (first three Bytes): 103.47.185., 202.157.134.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
|
| 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 |
| http://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.191.109.42
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.191.109.43
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://www.mytel.com.mm/ 202.191.109.42
|
| 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://www.mytel.com.mm/ 202.191.109.43
|
| 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://www.mytel.com.mm/ 202.191.109.42
|
| 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://www.mytel.com.mm/ 202.191.109.43
|
| 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://202.191.109.42/ 202.191.109.42
|
| 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://202.191.109.43/ 202.191.109.43
|
| 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 | 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 | Duration: 783580 milliseconds, 783.580 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)