Check DNS, Urls + Redirects, Certificates and Content of your Website




1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mytel.com.mm
A
202.191.109.42
Yangon/Rangoon/Myanmar (MM) - Telecom International Myanmar Company Limited
No Hostname found
yes
2
0

A
202.191.109.43
Yangon/Rangoon/Myanmar (MM) - Telecom International Myanmar Company Limited
No Hostname found
yes
2
0

AAAA

yes


www.mytel.com.mm
CNAME
mytel.com.mm
yes
1
0

A
202.191.109.42
Yangon/Rangoon/Myanmar (MM) - Telecom International Myanmar Company Limited
No Hostname found
yes



A
202.191.109.43
Yangon/Rangoon/Myanmar (MM) - Telecom International Myanmar Company Limited
No Hostname found
yes


*.mytel.com.mm
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 26838, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.08.2021, 00:00:00 +, Signature-Inception: 21.07.2021, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: mm
mm
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 18589, DigestType 2 and Digest CmZAPaLOtMOWB1BzkHTVynmTNLRcheP+3Xg44BokNdg=



1 RRSIG RR to validate DS RR found



RRSIG-Owner mm., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 07.08.2021, 17:00:00 +, Signature-Inception: 25.07.2021, 16:00:00 +, KeyTag 26838, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 26838 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 18589, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 32298, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner mm., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.07.2021, 18:00:34 +, Signature-Inception: 22.07.2021, 13:02:02 +, KeyTag 18589, Signer-Name: mm



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 18589 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 18589, DigestType 2 and Digest "CmZAPaLOtMOWB1BzkHTVynmTNLRcheP+3Xg44BokNdg=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com.mm
com.mm
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 22462, DigestType 2 and Digest VV5RdRmEhyI5ieA6LrgueLJ8dKty2PU8u+8fT1JILF8=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com.mm., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 31.07.2021, 05:28:11 +, Signature-Inception: 24.07.2021, 03:40:01 +, KeyTag 32298, Signer-Name: mm



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 32298 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 22462, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 65160, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com.mm., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 31.07.2021, 00:56:31 +, Signature-Inception: 24.07.2021, 01:06:01 +, KeyTag 22462, Signer-Name: com.mm



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 22462 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 22462, DigestType 2 and Digest "VV5RdRmEhyI5ieA6LrgueLJ8dKty2PU8u+8fT1JILF8=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: mytel.com.mm
mytel.com.mm
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "khf0a8s3cfhp2naiqf7ed17l848ln8ma" between the hashed NSEC3-owner "khf0a8s3cfhp2naiqf7ed17l848ln8ma" and the hashed NextOwner "khhcp72h2e47sc9h2rh3139ruuab6h1q". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner khf0a8s3cfhp2naiqf7ed17l848ln8ma.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 31.07.2021, 08:37:39 +, Signature-Inception: 23.07.2021, 19:42:01 +, KeyTag 65160, Signer-Name: com.mm



0 DNSKEY RR found




Zone: www.mytel.com.mm
www.mytel.com.mm
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
mytel.com.mm
  ns1.mtalk.net.mm
103.47.185.210
Yangon/Rangoon/Myanmar (MM) - Myanmar Technology Gateway Co., Ltd


  ns2.mtalk.net.mm
202.157.134.58
Queenstown Estate//Singapore (SG) - Iconz-Webvisions Pte. Ltd.

com.mm
  a.nic.net.mm / dns4.frpar1
37.209.192.4
Sterling/Virginia/United States (US) - NeuStar, Inc.


  b.nic.net.mm / dns1.defra1
37.209.194.4
Sterling/Virginia/United States (US) - NeuStar, Inc.


  c.nic.net.mm / dns2.defra1
37.209.196.4
Sterling/Virginia/United States (US) - NeuStar, Inc.


  d.nic.net.mm / dns2.frpar1
37.209.198.4
Sterling/Virginia/United States (US) - NeuStar, Inc.

mm
  a.nic.net.mm / dns2.frpar1


  b.nic.net.mm / dns1.defra1


  c.nic.net.mm / dns2.defra1


  d.nic.net.mm / dns3.frpar1


4. SOA-Entries


Domain:mm
Zone-Name:mm
Primary:a.nic.net.mm
Mail:admin.registry.gov.mm
Serial:1627273682
Refresh:1800
Retry:900
Expire:604800
TTL:3600
num Entries:4


Domain:com.mm
Zone-Name:com.mm
Primary:a.nic.net.mm
Mail:admin.registry.gov.mm
Serial:1627275242
Refresh:1800
Retry:900
Expire:604800
TTL:3600
num Entries:4


Domain:mytel.com.mm
Zone-Name:mytel.com.mm
Primary:ns1.mtalk.net.mm
Mail:noreply.mtg.com.mm
Serial:1476068603
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:2


5. Screenshots

Startaddress: https://www.mytel.com.mm, address used: https://www.mytel.com.mm/, Screenshot created 2021-07-26 07:13:47 +00:0

Mobil (412px x 732px)

831 milliseconds

Screenshot mobile - https://www.mytel.com.mm/
Mobil + Landscape (732px x 412px)

752 milliseconds

Screenshot mobile landscape - https://www.mytel.com.mm/
Screen (1280px x 1680px)

4853 milliseconds

Screenshot Desktop - https://www.mytel.com.mm/

Mobile- and other Chrome-Checks

widthheight
visual Viewport396732
content Size3966410

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.2, ECDHE_RSA with X25519, and AES_128_GCM.

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://mytel.com.mm/
202.191.109.42
403

Html is minified: 100.00 %
0.453
M
Forbidden
Content-Length: 19
Date: 26 Jul 2021 05:10:24 GMT
Content-Type: text/html
Server: Unknown

• http://mytel.com.mm/
202.191.109.43
403

Html is minified: 100.00 %
3.843
M
Forbidden
Content-Length: 19
Date: 26 Jul 2021 05:12:04 GMT
Content-Type: text/html
Server: Unknown

• http://www.mytel.com.mm/
202.191.109.42
200

Html is minified: 680.77 %
0.440
H
small visible content (num chars: 0)
Content-Length: 177
Date: 26 Jul 2021 05:10:28 GMT
Content-Type: text/html
Server: Unknown

• http://www.mytel.com.mm/
202.191.109.43
200

Html is minified: 680.77 %
0.437
H
small visible content (num chars: 0)
Content-Length: 177
Date: 26 Jul 2021 05:12:05 GMT
Content-Type: text/html
Server: Unknown

• https://mytel.com.mm/
202.191.109.42
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
403

Html is minified: 100.00 %
6.107
M
Forbidden
small visible content (num chars: 19)
Service unavailable
Content-Length: 19
Date: 26 Jul 2021 05:10:29 GMT
Content-Type: text/html
Server: Unknown

• https://mytel.com.mm/
202.191.109.43
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
403

Html is minified: 100.00 %
6.746
M
Forbidden
small visible content (num chars: 19)
Service unavailable
Content-Length: 19
Date: 26 Jul 2021 05:12:13 GMT
Content-Type: text/html
Server: Unknown

• https://www.mytel.com.mm/
202.191.109.42
Inline-JavaScript (∑/total): 1/134 Inline-CSS (∑/total): 0/0
200

Html is minified: 680.77 %
6.013
B
small visible content (num chars: 0)
Content-Length: 177
Date: 26 Jul 2021 05:10:44 GMT
Content-Type: text/html
Server: Unknown

• https://www.mytel.com.mm/
202.191.109.43
Inline-JavaScript (∑/total): 1/134 Inline-CSS (∑/total): 0/0
200

Html is minified: 680.77 %
23.453
B
small visible content (num chars: 0)
Content-Length: 177
Date: 26 Jul 2021 05:12:28 GMT
Content-Type: text/html
Server: Unknown

• http://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
202.191.109.42
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
403

Html is minified: 100.00 %
0.454
M
Forbidden
Visible Content: Service unavailable
Content-Length: 19
Date: 26 Jul 2021 05:11:14 GMT
Content-Type: text/html
Server: Unknown

• http://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
202.191.109.43
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
403

Html is minified: 100.00 %
0.436
M
Forbidden
Visible Content: Service unavailable
Content-Length: 19
Date: 26 Jul 2021 05:12:52 GMT
Content-Type: text/html
Server: Unknown

• http://www.mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
202.191.109.42
Inline-JavaScript (∑/total): 1/134 Inline-CSS (∑/total): 0/0
200

Html is minified: 680.77 %
0.450

Visible Content:
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
<html><body><script>document.cookie="D1N=8f22e6cd5dc37ccd0b7b706fb9ceac47"+"; expires=Fri, 31 Dec 2099 23:59:59 GMT; path=/";window.location.reload(true);</script></body></html>
Content-Length: 177
Date: 26 Jul 2021 05:11:15 GMT
Content-Type: text/html
Server: Unknown

• http://www.mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
202.191.109.43
Inline-JavaScript (∑/total): 1/134 Inline-CSS (∑/total): 0/0
200

Html is minified: 680.77 %
0.453

Visible Content:
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
<html><body><script>document.cookie="D1N=8f22e6cd5dc37ccd0b7b706fb9ceac47"+"; expires=Fri, 31 Dec 2099 23:59:59 GMT; path=/";window.location.reload(true);</script></body></html>
Content-Length: 177
Date: 26 Jul 2021 05:12:53 GMT
Content-Type: text/html
Server: Unknown

• https://202.191.109.42/
202.191.109.42
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 100.00 %
6.110
N
Certificate error: RemoteCertificateNameMismatch
small visible content (num chars: 16)
default response
Content-Length: 16
Date: 26 Jul 2021 05:11:16 GMT
Content-Type: text/html
Server: Unknown

• https://202.191.109.43/
202.191.109.43
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 100.00 %
6.153
N
Certificate error: RemoteCertificateNameMismatch
small visible content (num chars: 16)
default response
Content-Length: 16
Date: 26 Jul 2021 05:13:01 GMT
Content-Type: text/html
Server: Unknown

7. Comments


1. General Results, most used to calculate the result

Aname "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: 0 (complete: 151507)
Agood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: mytel.com.mm has 2 different ip addresses (authoritative).
AGood: 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.
Agood: No asked Authoritative Name Server had a timeout
Agood: one preferred version: www is preferred
AGood: 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.
AGood: 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
Bhttps://mytel.com.mm/ 202.191.109.42
403

Missing HSTS-Header
Bhttps://mytel.com.mm/ 202.191.109.43
403

Missing HSTS-Header
Bhttps://www.mytel.com.mm/ 202.191.109.42
200

Missing HSTS-Header
Bhttps://www.mytel.com.mm/ 202.191.109.43
200

Missing HSTS-Header
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
HFatal 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.
Mhttp://mytel.com.mm/ 202.191.109.42
403

Misconfiguration - main pages should never send http status 400 - 499
Mhttp://mytel.com.mm/ 202.191.109.43
403

Misconfiguration - main pages should never send http status 400 - 499
Mhttps://mytel.com.mm/ 202.191.109.42
403

Misconfiguration - main pages should never send http status 400 - 499
Mhttps://mytel.com.mm/ 202.191.109.43
403

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://202.191.109.42/ 202.191.109.42
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://202.191.109.43/ 202.191.109.43
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
AGood: 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.
AGood: 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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain mytel.com.mm, 2 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 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.mytel.com.mm, 2 ip addresses, 1 different http results.

2. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 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.
AGood: 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)
AGood (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 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.
AGood: Only one SOA.Primary Name Server found.: ns1.mtalk.net.mm.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.mtalk.net.mm.
AGood: 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
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: 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
AGood: Name servers with different Country locations found: 2 Name Servers, 2 Countries: MM, SG
AInfo: 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.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
AGood: 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.

3. Content- and Performance-critical Checks

http://www.mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.191.109.42
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.191.109.43
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html 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.42
403

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
403

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
200

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://www.mytel.com.mm/ 202.191.109.43
200

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://www.mytel.com.mm/ 202.191.109.42
200

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
200

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
200

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
200

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
200

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.
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 156653 milliseconds, 156.653 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
mytel.com.mm
202.191.109.42
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
mytel.com.mm
202.191.109.42
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)
1CN=*.mytel.com.mm, OU=IT, O="Telecom International Myanmar Co., Ltd", L=Yangon, C=MM, ST=Yangon

2CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

3CN=GlobalSign, OU=GlobalSign Root CA - R3, O=GlobalSign


mytel.com.mm
202.191.109.43
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

mytel.com.mm
202.191.109.43
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)
1CN=*.mytel.com.mm, OU=IT, O="Telecom International Myanmar Co., Ltd", L=Yangon, C=MM, ST=Yangon

2CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

3CN=GlobalSign, OU=GlobalSign Root CA - R3, O=GlobalSign


www.mytel.com.mm
202.191.109.42
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

www.mytel.com.mm
202.191.109.42
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)
1CN=*.mytel.com.mm, OU=IT, O="Telecom International Myanmar Co., Ltd", L=Yangon, C=MM, ST=Yangon

2CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

3CN=GlobalSign, OU=GlobalSign Root CA - R3, O=GlobalSign


www.mytel.com.mm
202.191.109.43
443
ok







ok

www.mytel.com.mm
202.191.109.43
443
ok








ok
 
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0

No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0


202.191.109.42
202.191.109.42
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

202.191.109.42
202.191.109.42
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)
1CN=*.mytel.com.mm, OU=IT, O="Telecom International Myanmar Co., Ltd", L=Yangon, C=MM, ST=Yangon

2CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

3CN=GlobalSign, OU=GlobalSign Root CA - R3, O=GlobalSign


202.191.109.43
202.191.109.43
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

202.191.109.43
202.191.109.43
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)
1CN=*.mytel.com.mm, OU=IT, O="Telecom International Myanmar Co., Ltd", L=Yangon, C=MM, ST=Yangon

2CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

3CN=GlobalSign, OU=GlobalSign Root CA - R3, O=GlobalSign


9. Certificates

1.
1.
CN=*.mytel.com.mm, O="Telecom International Myanmar Co., Ltd", OU=IT, L=Yangon, S=Yangon, C=MM
04.03.2020
20.04.2022
expires in 264 days
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm, mytel.com.mm - 6 entries
1.
1.
CN=*.mytel.com.mm, O="Telecom International Myanmar Co., Ltd", OU=IT, L=Yangon, S=Yangon, C=MM
04.03.2020

20.04.2022
expires in 264 days
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm, mytel.com.mm - 6 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:3A4D74517213FA1F8CAC29DB
Thumbprint:1DF74223661749CF341738ABD89A3B2E1333D863
SHA256 / Certificate:x7eOVFi3Tli0ZM7ZZkXrU5sKxpsgj2VIe8E7SfqcP4c=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):4d87cb42df724753a11e7a4db48669787faa58c4f1b6c6d00eb408443c8677e7
SHA256 hex / Subject Public Key Information (SPKI):57478e3670ff6e1f3397bb312e53380ff22990788e02ae7579190d01339fafb1
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.globalsign.com/gsrsaovsslca2018
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)


2.
CN=*.mytel.com.mm, O="Telecom International Myanmar Co., Ltd", OU=IT, L=Yangon, S=Yangon, C=MM
04.03.2020
20.04.2022
expires in 264 days
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm, mytel.com.mm - 6 entries

2.
CN=*.mytel.com.mm, O="Telecom International Myanmar Co., Ltd", OU=IT, L=Yangon, S=Yangon, C=MM
04.03.2020

20.04.2022
expires in 264 days
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm, mytel.com.mm - 6 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:3A4D74517213FA1F8CAC29DB
Thumbprint:1DF74223661749CF341738ABD89A3B2E1333D863
SHA256 / Certificate:x7eOVFi3Tli0ZM7ZZkXrU5sKxpsgj2VIe8E7SfqcP4c=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):4d87cb42df724753a11e7a4db48669787faa58c4f1b6c6d00eb408443c8677e7
SHA256 hex / Subject Public Key Information (SPKI):57478e3670ff6e1f3397bb312e53380ff22990788e02ae7579190d01339fafb1
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.globalsign.com/gsrsaovsslca2018
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)


3.
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
21.11.2018
21.11.2028
expires in 2671 days


3.
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
21.11.2018

21.11.2028
expires in 2671 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:01EE5F221DFC623BD4333A8557
Thumbprint:DFE83023062B997682708B4EAB8E819AFF5D9775
SHA256 / Certificate:tnb/oxeeiBIJOhter+6HauemqvIxB42tG/shzSiTdko=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp2.globalsign.com/rootr3
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


4.
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
21.11.2018
21.11.2028
expires in 2671 days


4.
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
21.11.2018

21.11.2028
expires in 2671 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:01EE5F221DFC623BD4333A8557
Thumbprint:DFE83023062B997682708B4EAB8E819AFF5D9775
SHA256 / Certificate:tnb/oxeeiBIJOhter+6HauemqvIxB42tG/shzSiTdko=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05
SHA256 hex / Subject Public Key Information (SPKI):23f2e981c1f8f6f5505ed935244c137f170b574837c91dedde2d90c60191a4c9
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp2.globalsign.com/rootr3
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


5.
CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
19.09.2018
28.01.2028
expires in 2373 days


5.
CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
19.09.2018

28.01.2028
expires in 2373 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:01EE5F169DFF97352B6465D66A
Thumbprint:0BBFAB97059595E8D1EC48E89EB8657C0E5AAE71
SHA256 / Certificate:RF7seLxhIVBEoDeWVqotXbXkL3bLcLjRTCB3qpQ9Trs=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80
SHA256 hex / Subject Public Key Information (SPKI):642e77667c356fdacbfeab009d30442cae4e01cdc0b9da61ae395c738ad62695
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.globalsign.com/rootr1
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


6.
CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
18.03.2009
18.03.2029
expires in 2788 days


6.
CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
18.03.2009

18.03.2029
expires in 2788 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:04000000000121585308A2
Thumbprint:D69B561148F01C77C54578C10926DF5B856976AD
SHA256 / Certificate:y7Ui17fxJ61qAROGW98c1BAufQdZr2NafPRyDcljxTs=
SHA256 hex / Cert (DANE * 0 1):cbb522d7b7f127ad6a0113865bdf1cd4102e7d0759af635a7cf4720dc963c53b
SHA256 hex / PublicKey (DANE * 1 1):706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80
SHA256 hex / Subject Public Key Information (SPKI):f623dcdb30748cc6dbc1125a470cc1ba77aad8367b5987e5ef15f8e916c3f1be
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:



7.
CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
01.09.1998
28.01.2028
expires in 2373 days


7.
CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
01.09.1998

28.01.2028
expires in 2373 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:040000000001154B5AC394
Thumbprint:B1BC968BD4F49D622AA89A81F2150152A41D829C
SHA256 / Certificate:69QQQOS7PsdCyeOB0x7ypBpItmhclufO88HfbNQzHJk=
SHA256 hex / Cert (DANE * 0 1):ebd41040e4bb3ec742c9e381d31ef2a41a48b6685c96e7cef3c1df6cd4331c99
SHA256 hex / PublicKey (DANE * 1 1):2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64
SHA256 hex / Subject Public Key Information (SPKI):9c2e43fc67f0e9410d9743f565520c9956d9ed5779c708e3a48dc1a874d37f64
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:



10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
0
0
7
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
0
2
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1472206024
precert
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
2020-03-04 03:17:02
2022-04-20 07:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm - 6 entries


1426712063
precert
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
2020-02-12 04:43:48
2022-04-20 07:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm - 6 entries


396390743
leaf cert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-05-21 16:57:02
2020-03-20 07:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm - 6 entries


337785872
leaf cert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-23 17:22:06
2020-03-20 07:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm - 6 entries


336691560
leaf cert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-22 15:42:02
2020-03-20 07:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm - 6 entries


336655963
precert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-22 15:17:06
2020-03-20 07:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm - 6 entries


336371623
leaf cert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-22 08:17:02
2020-03-20 07:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm - 6 entries


336223102
precert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-22 04:17:02
2020-03-20 07:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm - 6 entries


334609371
precert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-20 07:56:48
2020-03-20 07:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm - 6 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

Issuerlast 7 daysactivenum Certs
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
0
0
7
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
0
2
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2568252023
leaf cert
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
2020-03-04 02:17:02
2022-04-20 05:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm
6 entries


2445622586
precert
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
2020-02-12 03:43:48
2022-04-20 05:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm
6 entries


481739835
leaf cert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-05-21 14:57:02
2020-03-20 06:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm
6 entries


380724660
leaf cert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-23 16:22:06
2020-03-20 06:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm
6 entries


372209557
leaf cert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-22 14:42:02
2020-03-20 06:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm
6 entries


362318580
precert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-22 14:17:06
2020-03-20 06:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm
6 entries


372324536
leaf cert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-22 07:17:02
2020-03-20 06:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm
6 entries


361901841
precert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-22 03:17:02
2020-03-20 06:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm
6 entries


360249731
precert
CN=GlobalSign Organization Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE
2018-03-20 06:56:48
2020-03-20 06:56:48
*.mytel.com.mm, autodiscover.mytel.com.mm, mail.mytel.com.mm, mytel.com.mm, owa.mytel.com.mm, www.mytel.com.mm
6 entries



11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.mtalk.net.mm, ns2.mtalk.net.mm

QNr.DomainTypeNS used
1
mm
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.nic.net.mm, b.nic.net.mm, c.nic.net.mm, d.nic.net.mm
2
ns1.mtalk.net.mm: 103.47.185.210
NS
a.nic.net.mm (37.209.192.4)

Answer: ns2.mtalk.net.mm
202.157.134.58

Answer: ns3.mtalk.net.mm
203.81.168.71


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.mytel.com.mm



1
0
mytel.com.mm
0

no CAA entry found
1
0
com.mm
0

no CAA entry found
1
0
mm
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
mytel.com.mm
v=spf1 mx a ip4:103.85.104.3 -all
ok
1
0
www.mytel.com.mm
v=spf1 mx a ip4:103.85.104.3 -all
ok
1
0
_acme-challenge.mytel.com.mm

Name Error - The domain name does not exist
1
0
_acme-challenge.www.mytel.com.mm

Name Error - The domain name does not exist
1
0
_acme-challenge.mytel.com.mm.mytel.com.mm

Name Error - The domain name does not exist
1
0
_acme-challenge.www.mytel.com.mm.mytel.com.mm

Name Error - The domain name does not exist
1
0
_acme-challenge.www.mytel.com.mm.www.mytel.com.mm

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=d772e5bd-477a-4ce3-9f1a-c192e5926f6d


Last Result: https://check-your-website.server-daten.de/?q=mytel.com.mm - 2021-07-26 07:11:18


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=mytel.com.mm" target="_blank">Check this Site: mytel.com.mm</a>