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



O

old / weak connection

Checked:
13.09.2021 15:35:32


Older results

No older results found


1. IP-Addresses

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

AAAA

yes


www.ftth-payment.mytel.com.mm

Name Error
yes
1
0
*.mytel.com.mm
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.ftth-payment.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: 30.09.2021, 00:00:00 +, Signature-Inception: 09.09.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: 26.09.2021, 05:00:00 +, Signature-Inception: 13.09.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: 16.09.2021, 02:04:02 +, Signature-Inception: 08.09.2021, 20:45: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: 18.09.2021, 06:19:42 +, Signature-Inception: 11.09.2021, 08:25: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: 18.09.2021, 00:55:57 +, Signature-Inception: 11.09.2021, 09:53: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 "aclmq728ohk86uoe2t5egno8t72eaen3" between the hashed NSEC3-owner "aclmq728ohk86uoe2t5egno8t72eaen3" and the hashed NextOwner "acs2lmd7pphbphca976ghvtu3aq0jv1u". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner aclmq728ohk86uoe2t5egno8t72eaen3.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.09.2021, 14:49:16 +, Signature-Inception: 11.09.2021, 04:21:02 +, KeyTag 65160, Signer-Name: com.mm



0 DNSKEY RR found




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



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.ftth-payment.mytel.com.mm
  ns1.mtalk.net.mm

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

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:1631535002
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:1631539202
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:1476068613
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:2


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


Domain:www.ftth-payment.mytel.com.mm
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


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://ftth-payment.mytel.com.mm/
65.18.117.75
302
http://ftth-payment.mytel.com.mm/ftth/
0.593

Set-Cookie: JSESSIONID=BCB662651122AD3BBFB1DF377DE03C62; Path=/; HttpOnly
Location: http://ftth-payment.mytel.com.mm/ftth/
Content-Type: text/html
Content-Length: 0
Date: Mon, 16 Mar 2048 23:59:06 GMT
Connection: close

• http://ftth-payment.mytel.com.mm/ftth/

200

Html is minified: 145.56 %
0.923
H
Accept-Ranges: bytes
ETag: W/"7336-1577260781000"
Last-Modified: Wed, 25 Dec 2019 07:59:41 GMT
Content-Type: text/html
Content-Length: 7336
Date: Mon, 16 Mar 2048 23:59:06 GMT
Connection: close

• https://ftth-payment.mytel.com.mm/
65.18.117.75
302
http://ftth-payment.mytel.com.mm/ftth/
8.827
F
Set-Cookie: JSESSIONID=D5311DCF03781122FD3A864F285B5B39; Path=/; Secure; HttpOnly
Location: http://ftth-payment.mytel.com.mm/ftth/
Content-Type: text/html
Content-Length: 0
Date: Mon, 16 Mar 2048 23:59:06 GMT
Connection: close

• http://ftth-payment.mytel.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
65.18.117.75
404

Html is minified: 231.59 %
0.610
A
Visible Content: HTTP Status 404 – Not Found Type Status Report Message /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists. Apache Tomcat/9.0.14
Content-Type: text/html;charset=utf-8
Content-Language: en
Content-Length: 1151
Date: Mon, 16 Mar 2048 23:59:06 GMT
Connection: close

• https://65.18.117.75/
65.18.117.75
302
http://ftth-payment.mytel.com.mm/ftth/
8.607
N
Certificate error: RemoteCertificateNameMismatch
Set-Cookie: JSESSIONID=59AC9FD72960E0C0541A77E4DFA12A05; Path=/; Secure; HttpOnly
Location: http://ftth-payment.mytel.com.mm/ftth/
Content-Type: text/html
Content-Length: 0
Date: Mon, 16 Mar 2048 23:59:06 GMT
Connection: close

7. Comments


1. General Results, most used to calculate the result

Aname "ftth-payment.mytel.com.mm" is subdomain, 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
Warning: Only one ip address found: ftth-payment.mytel.com.mm has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: ftth-payment.mytel.com.mm has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
Agood - only one version with Http-Status 200
Agood: every cookie sent via https is marked as secure
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):1 complete Content-Type - header (2 urls)
http://ftth-payment.mytel.com.mm/ftth/


Url with incomplete Content-Type - header - missing charset
Bhttps://ftth-payment.mytel.com.mm/ 65.18.117.75
302

Missing HSTS-Header
http://ftth-payment.mytel.com.mm/ 65.18.117.75
302
JSESSIONID=BCB662651122AD3BBFB1DF377DE03C62; Path=/; HttpOnly
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
Bhttp://ftth-payment.mytel.com.mm/ 65.18.117.75
302
JSESSIONID=BCB662651122AD3BBFB1DF377DE03C62; Path=/; HttpOnly
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttps://ftth-payment.mytel.com.mm/ 65.18.117.75
302
JSESSIONID=D5311DCF03781122FD3A864F285B5B39; Path=/; Secure; HttpOnly
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttps://65.18.117.75/ 65.18.117.75
302
JSESSIONID=59AC9FD72960E0C0541A77E4DFA12A05; Path=/; Secure; HttpOnly
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Fhttps://ftth-payment.mytel.com.mm/ 65.18.117.75
302
http://ftth-payment.mytel.com.mm/ftth/
wrong redirect https - http - never redirect https to http
Fhttps://65.18.117.75/ 65.18.117.75
302
http://ftth-payment.mytel.com.mm/ftth/
wrong redirect https - http - never redirect https to http
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.
Nhttps://65.18.117.75/ 65.18.117.75
302
http://ftth-payment.mytel.com.mm/ftth/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch
OOld connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384. If your certificate has SHA256, first check your domain via ssllabs.com and update weak Cipher Suites. Forward Secrecy support is required. The part "Cipher Suites" should have a preference. First Cipher Suite with SHA instead of SHA256 or higher - that's the problem, change that. If that doesn't help, check if there is an old Firewall / router or something else, that supports only SHA1. Update that component.
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 ftth-payment.mytel.com.mm, 1 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: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 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

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 97497 milliseconds, 97.497 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
ftth-payment.mytel.com.mm
65.18.117.75
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha1
error checking OCSP stapling
weak
ftth-payment.mytel.com.mm
65.18.117.75
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha1
error checking OCSP stapling
weak
no http/2 via ALPN 
No SNI required - domain included in main certificate
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
No SNI required - domain included in main certificate
Tls.1.2
Tls.1.1
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


65.18.117.75
65.18.117.75
443
name does not match
Tls12
ECDH Ephermal
256
Aes256
256
Sha1
error checking OCSP stapling
weak

65.18.117.75
65.18.117.75
443
name does not match
Tls12

ECDH Ephermal
256
Aes256
256
Sha1
error checking OCSP stapling
weak
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
Tls.1.1
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 205 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 205 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):4d87cb42df724753a11e7a4db48669787faa58c4f1b6c6d00eb408443c8677e7
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 205 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 205 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):4d87cb42df724753a11e7a4db48669787faa58c4f1b6c6d00eb408443c8677e7
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 2612 days


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

21.11.2028
expires in 2612 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):8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05
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 2612 days


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

21.11.2028
expires in 2612 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):8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05
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 2314 days


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

28.01.2028
expires in 2314 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):706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80
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 2729 days


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

18.03.2029
expires in 2729 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):706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80
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 2314 days


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

28.01.2028
expires in 2314 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):2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64
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
k.root-servers.net (2001:7fd::1)

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
ftth-payment.mytel.com.mm
0

no CAA entry found
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
ftth-payment.mytel.com.mm

ok
1
0
_acme-challenge.ftth-payment.mytel.com.mm

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

Name Error - The domain name does not exist
1
0
_acme-challenge.ftth-payment.mytel.com.mm.ftth-payment.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=9656e8af-c0fa-4cba-9a39-4fce17431841


Last Result: https://check-your-website.server-daten.de/?q=ftth-payment.mytel.com.mm - 2021-09-13 15:35:32


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

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