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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
13.08.2023 10:35:08

Older results

T - 26.05.2023 07:58:32

T - 16.03.2023 03:00:05

T - 05.02.2023 15:21:20

T - 31.12.2022 17:15:15

T - 16.11.2022 17:22:09

T - 16.11.2022 16:45:19

T - 31.10.2022 10:47:53

T - 28.10.2022 09:35:38

T - 04.10.2022 06:03:30

T - 31.08.2022 13:09:56

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
ecare.ooredoo.com.mm	A	69.160.11.24 Yangon/Myanmar (MM) - Ooredoo Myanmar Limited No Hostname found	yes	1	0
	AAAA		yes
www.ecare.ooredoo.com.mm		Name Error	yes	1	0
*.ooredoo.com.mm	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.ecare.ooredoo.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 11019, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 31.08.2023, 00:00:00 +, Signature-Inception: 10.08.2023, 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.08.2023, 05:00:00 +, Signature-Inception: 13.08.2023, 04:00:00 +, KeyTag 11019, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 11019 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.08.2023, 13:28:06 +, Signature-Inception: 09.08.2023, 00:29: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: 16.08.2023, 09:14:58 +, Signature-Inception: 09.08.2023, 15:03: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: 16.08.2023, 23:01:31 +, Signature-Inception: 09.08.2023, 19:24: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: ooredoo.com.mm
ooredoo.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 "97c74h8in9ri44klel3769t9p3vi8iui" between the hashed NSEC3-owner "97c74h8in9ri44klel3769t9p3vi8iui" and the hashed NextOwner "97oasjbavc8maevoomd0fdm1hh3n4uaq". So the parent zone confirmes the not-existence of a DS RR. Bitmap: No Bitmap? Validated: RRSIG-Owner 97c74h8in9ri44klel3769t9p3vi8iui.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.08.2023, 01:44:39 +, Signature-Inception: 12.08.2023, 02:51:02 +, KeyTag 65160, Signer-Name: com.mm


	1 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 19206, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ooredoo.com.mm., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 17.08.2023, 00:00:00 +, Signature-Inception: 27.07.2023, 00:00:00 +, KeyTag 19206, Signer-Name: ooredoo.com.mm


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 19206 used to validate the DNSKEY RRSet


	Error: DNSKEY 19206 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.

Zone: ecare.ooredoo.com.mm
ecare.ooredoo.com.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 "ecare.ooredoo.com.mm" and the NextOwner "ecareapp.ooredoo.com.mm". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, RRSIG, NSEC


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 69.160.11.24 Validated: RRSIG-Owner ecare.ooredoo.com.mm., Algorithm: 13, 4 Labels, original TTL: 3600 sec, Signature-expiration: 17.08.2023, 00:00:00 +, Signature-Inception: 27.07.2023, 00:00:00 +, KeyTag 19206, Signer-Name: ooredoo.com.mm


	CNAME-Query sends a valid NSEC RR as result with the query name "ecare.ooredoo.com.mm" equal the NSEC-owner "ecare.ooredoo.com.mm" and the NextOwner "ecareapp.ooredoo.com.mm". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner ecare.ooredoo.com.mm., Algorithm: 13, 4 Labels, original TTL: 10800 sec, Signature-expiration: 17.08.2023, 00:00:00 +, Signature-Inception: 27.07.2023, 00:00:00 +, KeyTag 19206, Signer-Name: ooredoo.com.mm


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "ecare.ooredoo.com.mm" equal the NSEC-owner "ecare.ooredoo.com.mm" and the NextOwner "ecareapp.ooredoo.com.mm". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner ecare.ooredoo.com.mm., Algorithm: 13, 4 Labels, original TTL: 10800 sec, Signature-expiration: 17.08.2023, 00:00:00 +, Signature-Inception: 27.07.2023, 00:00:00 +, KeyTag 19206, Signer-Name: ooredoo.com.mm


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "ecare.ooredoo.com.mm" equal the NSEC-owner "ecare.ooredoo.com.mm" and the NextOwner "ecareapp.ooredoo.com.mm". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner ecare.ooredoo.com.mm., Algorithm: 13, 4 Labels, original TTL: 10800 sec, Signature-expiration: 17.08.2023, 00:00:00 +, Signature-Inception: 27.07.2023, 00:00:00 +, KeyTag 19206, Signer-Name: ooredoo.com.mm


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.ecare.ooredoo.com.mm) sends a valid NSEC RR as result with the owner name ecare.ooredoo.com.mm. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "ecare.ooredoo.com.mm" and the NextOwner "ecareapp.ooredoo.com.mm". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.ecare.ooredoo.com.mm) sends a valid NSEC RR as result with the query name "_443._tcp.ecare.ooredoo.com.mm" between the NSEC-owner "ecare.ooredoo.com.mm" and the NextOwner "ecareapp.ooredoo.com.mm". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.ecare.ooredoo.com.mm) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.ecare.ooredoo.com.mm" between the NSEC-owner "ecare.ooredoo.com.mm" and the NextOwner "ecareapp.ooredoo.com.mm". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner ecare.ooredoo.com.mm., Algorithm: 13, 4 Labels, original TTL: 10800 sec, Signature-expiration: 17.08.2023, 00:00:00 +, Signature-Inception: 27.07.2023, 00:00:00 +, KeyTag 19206, Signer-Name: ooredoo.com.mm


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "ecare.ooredoo.com.mm" equal the NSEC-owner "ecare.ooredoo.com.mm" and the NextOwner "ecareapp.ooredoo.com.mm". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner ecare.ooredoo.com.mm., Algorithm: 13, 4 Labels, original TTL: 10800 sec, Signature-expiration: 17.08.2023, 00:00:00 +, Signature-Inception: 27.07.2023, 00:00:00 +, KeyTag 19206, Signer-Name: ooredoo.com.mm


	Status: Good. NoData-Proof required and found.

Zone: www.ecare.ooredoo.com.mm
www.ecare.ooredoo.com.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 "ecare.ooredoo.com.mm" and the NextOwner "ecareapp.ooredoo.com.mm". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, RRSIG, NSEC

3. Name Servers

Domain	Nameserver	NS-IP
www.ecare.ooredoo.com.mm	• ns1.mtalk.net.mm
ecare.ooredoo.com.mm	• ns1.mtalk.net.mm	103.47.185.210 Yangon/Myanmar (MM) - Myanmar Technology Gateway Co.	•
ooredoo.com.mm	• ns1.mtalk.net.mm	103.47.185.210 Yangon/Myanmar (MM) - Myanmar Technology Gateway Co.	•
	T ns2.mtalk.net.mm	202.157.134.58 Singapore/Central Singapore/Singapore (SG) - Iconz-Webvisions Pte. Ltd.	•
com.mm	• a.nic.net.mm	37.209.192.4 Melbourne/Victoria/Australia (AU) - NeuStar, Inc.	•
	• b.nic.net.mm	37.209.194.4 Sydney/New South Wales/Australia (AU) - NeuStar, Inc.	•
	• c.nic.net.mm	37.209.196.4 Sydney/New South Wales/Australia (AU) - NeuStar, Inc.	•
	• d.nic.net.mm	37.209.198.4 Sydney/New South Wales/Australia (AU) - NeuStar, Inc.	•
	• ptd.net.mm	103.103.173.9 Nay Pyi Taw/Myanmar (MM) - Dept. of Information Technology & Cyber Security	•
mm	• a.nic.net.mm		•
	• b.nic.net.mm		•
	• c.nic.net.mm		•
	• d.nic.net.mm		•
	• ptd.net.mm		•

4. SOA-Entries

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

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

Domain:	ooredoo.com.mm
Zone-Name:	ooredoo.com.mm
Primary:	ns1.mtalk.net.mm
Mail:	zmo2004.gmail.com
Serial:	1474907232
Refresh:	10800
Retry:	3600
Expire:	604800
TTL:	10800
num Entries:	2

Domain:	ecare.ooredoo.com.mm
Zone-Name:	ooredoo.com.mm
Primary:	ns1.mtalk.net.mm
Mail:	zmo2004.gmail.com
Serial:	1474907232
Refresh:	10800
Retry:	3600
Expire:	604800
TTL:	10800
num Entries:	1

Domain:	www.ecare.ooredoo.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

Domainname	Http-Status	Sec.	G
• http://ecare.ooredoo.com.mm/ 69.160.11.24	-14	10.036	T
Timeout - The operation has timed out

• https://ecare.ooredoo.com.mm/ 69.160.11.24	-14	10.030	T
Timeout - The operation has timed out

• http://ecare.ooredoo.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.160.11.24	-14	10.034	T
Timeout - The operation has timed out
Visible Content:

• https://69.160.11.24/ 69.160.11.24	-14	10.037	T
Timeout - The operation has timed out

7. Comments

	1. General Results, most used to calculate the result
A	name "ecare.ooredoo.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: 1 (complete: 228216)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: ecare.ooredoo.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: ecare.ooredoo.com.mm has no ipv6 address.
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
	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 ecare.ooredoo.com.mm, 1 ip addresses.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.ecare.ooredoo.com.mm
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 2 Queries complete, 1 with IPv6, 1 with IPv4.
	Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
A	Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.mtalk.net.mm (103.47.185.210), ns2.mtalk.net.mm (202.157.134.58)
A	Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: ns1.mtalk.net.mm, ns2.mtalk.net.mm, 2 Name Servers included in Delegation: ns1.mtalk.net.mm, ns2.mtalk.net.mm, 2 Name Servers included in 1 Zone definitions: ns1.mtalk.net.mm, ns2.mtalk.net.mm, 1 Name Servers listed in SOA.Primary: ns1.mtalk.net.mm.
A	Good: Only one SOA.Primary Name Server found.: ns1.mtalk.net.mm.
A	Good: SOA.Primary Name Server included in the delegation set.: ns1.mtalk.net.mm.
A	Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.mtalk.net.mm, ns2.mtalk.net.mm
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
	Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found
	Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: *.mm
	Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: net.mm
A	Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: MM, SG
A	Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 103., 202., 2 different subnets (first two Bytes): 103.47., 202.157., 2 different subnets (first three Bytes): 103.47.185., 202.157.134.
A	Excellent: Every Name Server IPv4-address starts with an unique Byte.
A	Good: Nameserver supports TCP connections: 1 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 1 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
X	Nameserver Timeout checking EDNS512: ns2.mtalk.net.mm / 202.157.134.58
A	Good: All SOA have the same Serial Number
	Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
	4. Content- and Performance-critical Checks
	http://ecare.ooredoo.com.mm/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.160.11.24	-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.
A	Info: No img element found, no alt attribute checked
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 156910 milliseconds, 156.910 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)

Issuer				last 7 days	active	num Certs
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US				0	1	3
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US				0	1	2
CN=DigiCert Basic RSA CN CA G2, O=DigiCert Inc, C=US				0	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
5801513778 leaf cert	CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2023-09-05 00:00:00	2024-07-13 23:59:59	*.ooredoo.com.mm, dealerapp.ooredoo.com.mm, dse.ooredoo.com.mm, ecareapp.ooredoo.com.mm, ecarepreprod.ooredoo.com.mm, ooredoo.com.mm, promoter.ooredoo.com.mm, salesforceapp.ooredoo.com.mm - 8 entries
5316719754 precert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2023-06-01 00:00:00	2024-06-30 23:59:59	*.ooredoo.com.mm, ooredoo.com.mm - 2 entries
4697175322 precert	CN=DigiCert Basic RSA CN CA G2, O=DigiCert Inc, C=US	2023-01-18 00:00:00	2024-01-18 23:59:59	*.ooredoo.com.mm, ooredoo.com.mm - 2 entries
4089221485 precert	CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-08-22 00:00:00	2023-09-22 23:59:59	*.ooredoo.com.mm, dealerapp.ooredoo.com.mm, dse.ooredoo.com.mm, ecareapp.ooredoo.com.mm, ecarepreprod.ooredoo.com.mm, ooredoo.com.mm, promoter.ooredoo.com.mm, salesforceapp.ooredoo.com.mm - 8 entries
3938030239 precert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-07-12 00:00:00	2023-08-12 23:59:59	*.ooredoo.com.mm, dealerapp.ooredoo.com.mm, dse.ooredoo.com.mm, ecareapp.ooredoo.com.mm, ecarepreprod.ooredoo.com.mm, ooredoo.com.mm, promoter.ooredoo.com.mm, salesforceapp.ooredoo.com.mm - 8 entries
3719994052 precert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-05-12 00:00:00	2023-06-12 23:59:59	*.ooredoo.com.mm, ooredoo.com.mm - 2 entries

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

Issuer				last 7 days	active	num Certs
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US				0	1	3
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US				0	1	2
CN=DigiCert Basic RSA CN CA G2, O=DigiCert Inc, C=US				0	1	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
10562248837 leaf cert	CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2023-09-04 22:00:00	2024-07-13 21:59:59	*.ooredoo.com.mm, dealerapp.ooredoo.com.mm, dse.ooredoo.com.mm, ecareapp.ooredoo.com.mm, ecarepreprod.ooredoo.com.mm, ooredoo.com.mm, promoter.ooredoo.com.mm, salesforceapp.ooredoo.com.mm 8 entries
9540999906 precert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2023-05-31 22:00:00	2024-06-30 21:59:59	*.ooredoo.com.mm, ooredoo.com.mm 2 entries
8436044742 precert	CN=DigiCert Basic RSA CN CA G2, O=DigiCert Inc, C=US	2023-01-17 23:00:00	2024-01-18 22:59:59	*.ooredoo.com.mm, ooredoo.com.mm 2 entries
7385046726 precert	CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-08-21 22:00:00	2023-09-22 21:59:59	*.ooredoo.com.mm, dealerapp.ooredoo.com.mm, dse.ooredoo.com.mm, ecareapp.ooredoo.com.mm, ecarepreprod.ooredoo.com.mm, ooredoo.com.mm, promoter.ooredoo.com.mm, salesforceapp.ooredoo.com.mm 8 entries
9038531410 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-07-11 22:00:00	2023-08-12 21:59:59	*.ooredoo.com.mm, dealerapp.ooredoo.com.mm, dse.ooredoo.com.mm, ecareapp.ooredoo.com.mm, ecarepreprod.ooredoo.com.mm, ooredoo.com.mm, promoter.ooredoo.com.mm, salesforceapp.ooredoo.com.mm 8 entries
6855993104 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-05-11 22:00:00	2023-06-12 21:59:59	*.ooredoo.com.mm, ooredoo.com.mm 2 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.	Domain	Type	NS 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, ptd.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

Domainname	Value	∑ Queries	∑ Timeout
ecare.ooredoo.com.mm	no CAA entry found	1	0
ooredoo.com.mm	no CAA entry found	2	1
com.mm	no CAA entry found	1	0
mm	no CAA entry found	1	0

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries	∑ Timeout
ooredoo.com.mm	google-site-verification=ENAfDqkI5P6X_PXNUHcnK4xJ-y2BHrOdoiCo-dTPIoo	ok	1	0
ooredoo.com.mm	MS=ms91879998	ok	1	0
ooredoo.com.mm	tmDdfBJywlnN5QEwMiX7dNnMthBvI3PzxwsyXvIxdRjqg8APIJAfdZOpv/Lpz4olCOs817oRNO1fHeiVQFv3WA==	ok	1	0
ooredoo.com.mm	v=spf1 include:spf.protection.outlook.com ip4:103.242.99.15 ip4:103.242.99.1 ip4:103.242.99.2 ip4:69.160.11.33 -all	ok	1	0
ecare.ooredoo.com.mm		ok	1	0
_acme-challenge.ecare.ooredoo.com.mm		Name Error - The domain name does not exist	2	1
_acme-challenge.ecare.ooredoo.com.mm.ooredoo.com.mm		Name Error - The domain name does not exist	1	0
_acme-challenge.ecare.ooredoo.com.mm.ecare.ooredoo.com.mm		Name Error - The domain name does not exist	2	1

15. DomainService - Entries

No DomainServiceEntries entries found

16. Cipher Suites

No results

17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=d0be7469-fdda-499b-9374-df0c70f4fec1

Last Result: https://check-your-website.server-daten.de/?q=ecare.ooredoo.com.mm - 2023-11-14 19:02:03

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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro