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: 12.08.2021, 05:00:00 +, Signature-Inception: 30.07.2021, 04: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: 03.08.2021, 07:07:41 +, Signature-Inception: 27.07.2021, 17:02:01 +, 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: 04.08.2021, 19:48:42 +, Signature-Inception: 29.07.2021, 04:37:02 +, 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: 05.08.2021, 03:38:05 +, Signature-Inception: 29.07.2021, 00:06:02 +, 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: 04.08.2021, 20:46:48 +, Signature-Inception: 29.07.2021, 07:38: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
37.209.192.4
Sterling/Virginia/United States (US) - NeuStar, Inc.


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


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


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

mm
  a.nic.net.mm


  b.nic.net.mm


  c.nic.net.mm


  d.nic.net.mm


4. SOA-Entries


Domain:mm
Zone-Name:mm
Primary:a.nic.net.mm
Mail:admin.registry.gov.mm
Serial:1627663382
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:1627666681
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:1476068604
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:2


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

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

Html is minified: 100.00 %
0.436
M
Forbidden
Content-Length: 19
Date: 30 Jul 2021 17:46:37 GMT
Content-Type: text/html
Server: Unknown

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

Html is minified: 100.00 %
3.857
M
Forbidden
Content-Length: 19
Date: 30 Jul 2021 17:48:22 GMT
Content-Type: text/html
Server: Unknown

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

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

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

Html is minified: 680.77 %
0.423
H
small visible content (num chars: 0)
Content-Length: 177
Date: 30 Jul 2021 17:48:23 GMT
Content-Type: text/html
Server: Unknown

• https://mytel.com.mm:80/
202.191.109.42
-14

10.033
T
Timeout - The operation has timed out

• https://mytel.com.mm:80/
202.191.109.43
-14

10.017
T
Timeout - The operation has timed out

• https://www.mytel.com.mm:80/
202.191.109.42
-14

10.026
T
Timeout - The operation has timed out

• https://www.mytel.com.mm:80/
202.191.109.43
-14

10.030
T
Timeout - The operation has timed out

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

Html is minified: 100.00 %
0.420
M
Forbidden
Visible Content: Service unavailable
Content-Length: 19
Date: 30 Jul 2021 17:47:23 GMT
Content-Type: text/html
Server: Unknown

• http://mytel.com.mm:80/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
202.191.109.43
403

Html is minified: 100.00 %
0.436
M
Forbidden
Visible Content: Service unavailable
Content-Length: 19
Date: 30 Jul 2021 17:49:03 GMT
Content-Type: text/html
Server: Unknown

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

Html is minified: 680.77 %
0.437

Visible Content:
Content-Length: 177
Date: 30 Jul 2021 17:47:24 GMT
Content-Type: text/html
Server: Unknown

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

Html is minified: 680.77 %
0.406

Visible Content:
Content-Length: 177
Date: 30 Jul 2021 17:49:05 GMT
Content-Type: text/html
Server: Unknown

• https://202.191.109.42:80/
202.191.109.42
-14

10.013
T
Timeout - The operation has timed out

• https://202.191.109.43:80/
202.191.109.43
-14

10.027
T
Timeout - The operation has timed out

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: 168171)
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 - only one version with Http-Status 200
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 (8 urls)
http://mytel.com.mm:80/ 202.191.109.42


Url with incomplete Content-Type - header - missing charset
http://mytel.com.mm:80/ 202.191.109.43


Url with incomplete Content-Type - header - missing charset
http://www.mytel.com.mm:80/ 202.191.109.42


Url with incomplete Content-Type - header - missing charset
http://www.mytel.com.mm:80/ 202.191.109.43


Url with incomplete Content-Type - header - missing charset
http://mytel.com.mm:80/.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:80/.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:80/.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:80/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.191.109.43


Url with incomplete Content-Type - header - missing charset
Hfatal error: No https - result with http-status 200, no encryption
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:80/ 202.191.109.42
403

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

Misconfiguration - main pages should never send http status 400 - 499
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 the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain mytel.com.mm, 2 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.mytel.com.mm, 2 ip addresses.

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, 0 with IPv6, 2 with IPv4.
Error: No DNS Query 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: 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://mytel.com.mm:80/.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:80/.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.
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: 132794 milliseconds, 132.794 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


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
j.root-servers.net (192.58.128.30)

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=9a00ccdb-2193-4a5c-ad14-4abf2583434e


Last Result: https://check-your-website.server-daten.de/?q=mytel.com.mm%3a80 - 2021-07-30 19:47:45


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%3a80" target="_blank">Check this Site: mytel.com.mm:80</a>