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




1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mytel.com.mm
A
103.85.107.172
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
103.85.107.172
Yangon/Rangoon/Myanmar (MM) - Telecom International Myanmar Company Limited
No Hostname found
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



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 33853, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2020, 00:00:00 +, Signature-Inception: 11.01.2020, 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
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "mm" and the NextOwner "mma". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC



0 DNSKEY RR found




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



0 DNSKEY RR found




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



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
203.81.168.71
Yatanarpon Cyber City/Mandalay Region/Myanmar (MM) - Yatanarpon Teleport Company Limited

com.mm
  a.nic.net.mm


  b.nic.net.mm


  c.nic.net.mm


  d.nic.net.mm

mm
  a.nic.net.mm


  b.nic.net.mm


  c.nic.net.mm


  d.nic.net.mm


4. SOA-Entries


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


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


Domain:mytel.com.mm
Zone-Name:
Primary:ns1.mtalk.net.mm
Mail:noreply.mtg.com.mm
Serial:1476068445
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/
103.85.107.172
301
https://mytel.com.mm/
Html is minified: 108.19 %
0.467
A
Server: nginx/1.10.2
Date: Fri, 17 Jan 2020 05:56:31 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://mytel.com.mm/

• http://www.mytel.com.mm/
103.85.107.172
301
https://mytel.com.mm/
Html is minified: 108.19 %
3.467
E
Server: nginx/1.10.2
Date: Fri, 17 Jan 2020 05:56:35 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://mytel.com.mm/

• https://mytel.com.mm/
103.85.107.172
-14

10.020
T
Timeout - The operation has timed out

• https://www.mytel.com.mm/
103.85.107.172
-1

49.727
U
Interner Fehler: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 103.85.107.172:443

• http://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
103.85.107.172
301
https://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 108.19 %
3.483
A
Visible Content:
Server: nginx/1.10.2
Date: Fri, 17 Jan 2020 05:57:38 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
103.85.107.172
301
https://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 108.19 %
0.466
E
Visible Content:
Server: nginx/1.10.2
Date: Fri, 17 Jan 2020 05:57:38 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-14

10.010
T
Timeout - The operation has timed out
Visible Content:

7. Comments


1. General Results, most used to calculate the result

Aname "mytel.com.mm" is subdomain, public suffix is "*.mm", top-level-domain-type is "country-code", Country is Myanmar, tld-manager is "Ministry of Transport and Communications"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
CError - no version with Http-Status 200
Ehttp://www.mytel.com.mm/ 103.85.107.172
301
https://mytel.com.mm/
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, 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.
Hfatal error: No https - result with http-status 200, no encryption

2. DNS- and NameServer - Checks

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: 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

https://mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 121010 milliseconds, 121.010 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:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


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
com.mm

Refused - The name server refuses to perform the specified operation for policy reasons
1
0
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.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=bcb166f1-ba03-4143-bcef-f261a2d0544d


Last Result: https://check-your-website.server-daten.de/?q=mytel.com.mm - 2020-07-21 23:15:50


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>