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

0 in Queue, 0 of max. 8 Checks (05:11:57)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

P

 

Tls-Protocol error

 

Checked:
12.12.2025 22:24:39

 

Older results

 

P - 26.07.2025 16:32:15
P - 26.07.2025 16:22:43
P - 25.06.2025 13:10:09
P - 15.04.2025 03:55:57
P - 07.04.2025 01:16:42
P - 06.04.2025 00:30:19
P - 04.11.2024 14:38:12
P - 29.06.2024 08:24:12
P - 15.04.2024 23:35:42
P - 15.04.2024 23:31:24

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
ooredoo.com
A
20.21.128.2
Doha/Baladiyat ad Dawhah/Qatar (QA) - Microsoft Corporation
No Hostname found
yes
1
0

AAAA

yes


www.ooredoo.com
CNAME
www.ooredoo.com.cdn.cloudflare.net
yes
1
0

A
104.20.38.150
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.
No Hostname found
yes



A
172.66.147.2
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.
No Hostname found
yes


*.ooredoo.com
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






3 DNSKEY RR found






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






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






Public Key with Algorithm 8, KeyTag 61809, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 31.12.2025, 00:00:00 +, Signature-Inception: 10.12.2025, 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: com

com
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.12.2025, 17:00:00 +, Signature-Inception: 12.12.2025, 16:00:00 +, KeyTag 61809, Signer-Name: (root)






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






2 DNSKEY RR found






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






Public Key with Algorithm 13, KeyTag 46539, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.12.2025, 15:02:35 +, Signature-Inception: 08.12.2025, 14:57:35 +, KeyTag 19718, Signer-Name: com






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






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



Zone: ooredoo.com

ooredoo.com
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 "5at12a1kar6gdtko8fhqikf1kielhvli" between the hashed NSEC3-owner "5at102hhil8dn0dgtngdi24psbgbd37e" and the hashed NextOwner "5at17abtrijotftm722hm4sgkcgrs3o7". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 5at102hhil8dn0dgtngdi24psbgbd37e.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 18.12.2025, 08:04:45 +, Signature-Inception: 11.12.2025, 06:54:45 +, KeyTag 46539, Signer-Name: com






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q3udg8cekkae7rukpgct1dvssh8ll". So that domain name is the Closest Encloser of "ooredoo.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 17.12.2025, 00:27:03 +, Signature-Inception: 09.12.2025, 23:17:03 +, KeyTag 46539, Signer-Name: com






0 DNSKEY RR found









Zone: www.ooredoo.com

www.ooredoo.com
0 DS RR in the parent zone found



Zone: (root)

(root)
1 DS RR published






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






• Status: Valid because published






3 DNSKEY RR found






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






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






Public Key with Algorithm 8, KeyTag 61809, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 31.12.2025, 00:00:00 +, Signature-Inception: 10.12.2025, 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: net

net
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=






1 RRSIG RR to validate DS RR found






RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.12.2025, 17:00:00 +, Signature-Inception: 12.12.2025, 16:00:00 +, KeyTag 61809, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 17133, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.12.2025, 15:10:35 +, Signature-Inception: 08.12.2025, 15:05:35 +, KeyTag 37331, Signer-Name: net






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






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: cloudflare.net

cloudflare.net
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 2371, DigestType 2 and Digest kPcQoQfaUe14El0wpocEzzwDCK/QG/zXBX1L0Dtixos=






1 RRSIG RR to validate DS RR found






RRSIG-Owner cloudflare.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.12.2025, 03:23:35 +, Signature-Inception: 12.12.2025, 02:13:35 +, KeyTag 17133, Signer-Name: net






• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 17133 used to validate the DS RRSet in the parent zone






2 DNSKEY RR found






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






Public Key with Algorithm 13, KeyTag 34505, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner cloudflare.net., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 04.02.2026, 08:04:27 +, Signature-Inception: 05.12.2025, 08:04:27 +, KeyTag 2371, Signer-Name: cloudflare.net






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






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 2371, DigestType 2 and Digest "kPcQoQfaUe14El0wpocEzzwDCK/QG/zXBX1L0Dtixos=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: cdn.cloudflare.net

cdn.cloudflare.net
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 "cdn.cloudflare.net" and the NextOwner "\000.cdn.cloudflare.net". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA






0 DNSKEY RR found









Zone: com.cdn.cloudflare.net

com.cdn.cloudflare.net
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 "com.cdn.cloudflare.net" and the NextOwner "\000.com.cdn.cloudflare.net". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA






0 DNSKEY RR found









Zone: ooredoo.com.cdn.cloudflare.net

ooredoo.com.cdn.cloudflare.net
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 "ooredoo.com.cdn.cloudflare.net" and the NextOwner "\000.ooredoo.com.cdn.cloudflare.net". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA






0 DNSKEY RR found









Zone: www.ooredoo.com.cdn.cloudflare.net

www.ooredoo.com.cdn.cloudflare.net
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 "www.ooredoo.com.cdn.cloudflare.net" and the NextOwner "\000.www.ooredoo.com.cdn.cloudflare.net". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 104.20.38.150 172.66.147.2
Validated: RRSIG-Owner www.ooredoo.com.cdn.cloudflare.net., Algorithm: 13, 6 Labels, original TTL: 300 sec, Signature-expiration: 13.12.2025, 22:25:53 +, Signature-Inception: 11.12.2025, 20:25:53 +, KeyTag 34505, Signer-Name: cloudflare.net






CNAME-Query sends a valid NSEC RR as result with the query name "www.ooredoo.com.cdn.cloudflare.net" equal the NSEC-owner "www.ooredoo.com.cdn.cloudflare.net" and the NextOwner "\000.www.ooredoo.com.cdn.cloudflare.net". 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, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner www.ooredoo.com.cdn.cloudflare.net., Algorithm: 13, 6 Labels, original TTL: 1800 sec, Signature-expiration: 13.12.2025, 22:25:53 +, Signature-Inception: 11.12.2025, 20:25:53 +, KeyTag 34505, Signer-Name: cloudflare.net






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC RR as result with the query name "www.ooredoo.com.cdn.cloudflare.net" equal the NSEC-owner "www.ooredoo.com.cdn.cloudflare.net" and the NextOwner "\000.www.ooredoo.com.cdn.cloudflare.net". 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, 13, MX, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner www.ooredoo.com.cdn.cloudflare.net., Algorithm: 13, 6 Labels, original TTL: 1800 sec, Signature-expiration: 13.12.2025, 22:25:53 +, Signature-Inception: 11.12.2025, 20:25:53 +, KeyTag 34505, Signer-Name: cloudflare.net






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC RR as result with the query name "www.ooredoo.com.cdn.cloudflare.net" equal the NSEC-owner "www.ooredoo.com.cdn.cloudflare.net" and the NextOwner "\000.www.ooredoo.com.cdn.cloudflare.net". 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, 13, MX, TXT, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner www.ooredoo.com.cdn.cloudflare.net., Algorithm: 13, 6 Labels, original TTL: 5 sec, Signature-expiration: 13.12.2025, 22:25:53 +, Signature-Inception: 11.12.2025, 20:25:53 +, KeyTag 34505, Signer-Name: cloudflare.net






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.www.ooredoo.com.cdn.cloudflare.net) sends a valid NSEC RR as result with the query name "_443._tcp.www.ooredoo.com.cdn.cloudflare.net" equal the NSEC-owner "_443._tcp.www.ooredoo.com.cdn.cloudflare.net" and the NextOwner "\000._443._tcp.www.ooredoo.com.cdn.cloudflare.net". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner _443._tcp.www.ooredoo.com.cdn.cloudflare.net., Algorithm: 13, 8 Labels, original TTL: 1800 sec, Signature-expiration: 13.12.2025, 22:25:53 +, Signature-Inception: 11.12.2025, 20:25:53 +, KeyTag 34505, Signer-Name: cloudflare.net






Status: Good. NoData-Proof required and found.






CAA-Query sends a valid NSEC RR as result with the query name "www.ooredoo.com.cdn.cloudflare.net" equal the NSEC-owner "www.ooredoo.com.cdn.cloudflare.net" and the NextOwner "\000.www.ooredoo.com.cdn.cloudflare.net". 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, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI Validated: RRSIG-Owner www.ooredoo.com.cdn.cloudflare.net., Algorithm: 13, 6 Labels, original TTL: 1800 sec, Signature-expiration: 13.12.2025, 22:25:53 +, Signature-Inception: 11.12.2025, 20:25:53 +, KeyTag 34505, Signer-Name: cloudflare.net






Status: Good. NoData-Proof required and found.

 

3. Name Servers

DomainNameserverNS-IP
ooredoo.com
•  dns1.qatar.net.qa
212.77.192.28
Doha/Baladīyat ad Dawḩah/Qatar (QA) - OOREDOO IP		•

•  dns2.qatar.net.qa
212.77.192.30
Doha/Baladīyat ad Dawḩah/Qatar (QA) - OOREDOO IP		•

•  dns3.qatar.net.qa
3.69.128.92
Frankfurt am Main/Hesse/Germany (DE) - Amazon Technologies Inc.		•
com
•  a.gtld-servers.net
•

•  b.gtld-servers.net
•

•  c.gtld-servers.net
•

•  d.gtld-servers.net
•

•  e.gtld-servers.net
•

•  f.gtld-servers.net
•

•  g.gtld-servers.net
•

•  h.gtld-servers.net
•

•  i.gtld-servers.net
•

•  j.gtld-servers.net
•

•  k.gtld-servers.net
•

•  l.gtld-servers.net
•

•  m.gtld-servers.net
•
www.ooredoo.com.cdn.cloudflare.net
•  ns1.cloudflare.net
108.162.198.250
Ashburn/Virginia/United States (US) - Cloudflare, Inc.		•

• 
162.159.60.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
172.64.40.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:57:1:4e4b:27d7:a29f:3cfa
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

• 
2803:f800:52:1:1df9:cfa1:ac40:28fa
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.		•

• 
2a06:98c1:56:1:2693:f8af:6ca2:c6fa
London/England/United Kingdom (GB) - Cloudflare, Inc.		•
ooredoo.com.cdn.cloudflare.net
•  ns1.cloudflare.net
108.162.198.250
Ashburn/Virginia/United States (US) - Cloudflare, Inc.		•

• 
162.159.60.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
172.64.40.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:57:1:4e4b:27d7:a29f:3cfa
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

• 
2803:f800:52:1:1df9:cfa1:ac40:28fa
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.		•

• 
2a06:98c1:56:1:2693:f8af:6ca2:c6fa
London/England/United Kingdom (GB) - Cloudflare, Inc.		•
com.cdn.cloudflare.net
•  ns1.cloudflare.net
108.162.198.250
Ashburn/Virginia/United States (US) - Cloudflare, Inc.		•

• 
162.159.60.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
172.64.40.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:57:1:4e4b:27d7:a29f:3cfa
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

• 
2803:f800:52:1:1df9:cfa1:ac40:28fa
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.		•

• 
2a06:98c1:56:1:2693:f8af:6ca2:c6fa
London/England/United Kingdom (GB) - Cloudflare, Inc.		•
cdn.cloudflare.net
•  ns1.cloudflare.net
108.162.198.250
Ashburn/Virginia/United States (US) - Cloudflare, Inc.		•

• 
162.159.60.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
172.64.40.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:57:1:4e4b:27d7:a29f:3cfa
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

• 
2803:f800:52:1:1df9:cfa1:ac40:28fa
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.		•

• 
2a06:98c1:56:1:2693:f8af:6ca2:c6fa
London/England/United Kingdom (GB) - Cloudflare, Inc.		•
cloudflare.net
•  ns1.cloudflare.net
108.162.198.250
Ashburn/Virginia/United States (US) - Cloudflare, Inc.		•

• 
162.159.60.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
172.64.40.250
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:57:1:4e4b:27d7:a29f:3cfa
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

• 
2803:f800:52:1:1df9:cfa1:ac40:28fa
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.		•

• 
2a06:98c1:56:1:2693:f8af:6ca2:c6fa
London/England/United Kingdom (GB) - Cloudflare, Inc.		•

•  ns2.cloudflare.net
108.162.198.251
Ashburn/Virginia/United States (US) - Cloudflare, Inc.		•

• 
162.159.60.251
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
172.64.40.251
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:57:1:e6ea:b99c:a29f:3cfb
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

• 
2803:f800:52:1:4da:414e:ac40:28fb
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.		•

• 
2a06:98c1:56:1:ca7d:4c29:6ca2:c6fb
London/England/United Kingdom (GB) - Cloudflare, Inc.		•

•  ns3.cloudflare.net
108.162.198.252
Ashburn/Virginia/United States (US) - Cloudflare, Inc.		•

• 
162.159.60.252
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
172.64.40.252
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:57:1:cba:4d93:a29f:3cfc
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

• 
2803:f800:52:1:b216:ccbe:ac40:28fc
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.		•

• 
2a06:98c1:56:1:2cfa:9492:6ca2:c6fc
London/England/United Kingdom (GB) - Cloudflare, Inc.		•

•  ns4.cloudflare.net
108.162.198.253
Ashburn/Virginia/United States (US) - Cloudflare, Inc.		•

• 
162.159.60.253
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
172.64.40.253
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:57:1:fd14:b411:a29f:3cfd
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

• 
2803:f800:52:1:e69e:46f0:ac40:28fd
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.		•

• 
2a06:98c1:56:1:45a3:de4a:6ca2:c6fd
London/England/United Kingdom (GB) - Cloudflare, Inc.		•

•  ns5.cloudflare.net
108.162.198.254
Ashburn/Virginia/United States (US) - Cloudflare, Inc.		•

• 
162.159.60.254
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
172.64.40.254
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:57:1:cb7b:a51d:a29f:3cfe
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

• 
2803:f800:52:1:d48b:2cd:ac40:28fe
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.		•

• 
2a06:98c1:56:1:3b6c:6602:6ca2:c6fe
London/England/United Kingdom (GB) - Cloudflare, Inc.		•
net
•  a.gtld-servers.net
•

•  b.gtld-servers.net
•

•  c.gtld-servers.net
•

•  d.gtld-servers.net
•

•  e.gtld-servers.net
•

•  f.gtld-servers.net
•

•  g.gtld-servers.net
•

•  h.gtld-servers.net
•

•  i.gtld-servers.net
•

•  j.gtld-servers.net
•

•  k.gtld-servers.net
•

•  l.gtld-servers.net
•

•  m.gtld-servers.net
•

 

4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1765574650
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:6


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1765574665
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:7


Domain:ooredoo.com
Zone-Name:ooredoo.com
Primary:dns1.qatar.net.qa
Mail:empty.empty
Serial:2023041394
Refresh:3600
Retry:600
Expire:1209600
TTL:3600
num Entries:3


Domain:net
Zone-Name:net
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1765574680
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:13


Domain:cloudflare.net
Zone-Name:cloudflare.net
Primary:ns1.cloudflare.net
Mail:dns.cloudflare.com
Serial:2390493972
Refresh:10000
Retry:2400
Expire:604800
TTL:1800
num Entries:30


Domain:cdn.cloudflare.net
Zone-Name:cloudflare.net
Primary:ns1.cloudflare.net
Mail:dns.cloudflare.com
Serial:2390493972
Refresh:10000
Retry:2400
Expire:604800
TTL:1800
num Entries:6


Domain:com.cdn.cloudflare.net
Zone-Name:cloudflare.net
Primary:ns1.cloudflare.net
Mail:dns.cloudflare.com
Serial:2390493972
Refresh:10000
Retry:2400
Expire:604800
TTL:1800
num Entries:6


Domain:ooredoo.com.cdn.cloudflare.net
Zone-Name:cloudflare.net
Primary:ns1.cloudflare.net
Mail:dns.cloudflare.com
Serial:2390493972
Refresh:10000
Retry:2400
Expire:604800
TTL:1800
num Entries:6


Domain:www.ooredoo.com.cdn.cloudflare.net
Zone-Name:cloudflare.net
Primary:ns1.cloudflare.net
Mail:dns.cloudflare.com
Serial:2390493972
Refresh:10000
Retry:2400
Expire:604800
TTL:1800
num Entries:6


5. Screenshots

Startaddress: https://www.ooredoo.com/, address used: https://www.ooredoo.com/, Screenshot created 2023-05-02 23:29:29 +00:0 url is insecure, certificate invalid

 

Mobil (412px x 732px)

 

243 milliseconds

 

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

 

308 milliseconds

 

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

 

419 milliseconds

 

Screenshot Desktop - https://www.ooredoo.com/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size412732

 

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

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://ooredoo.com/
20.21.128.2
301
https://www.ooredoo.com/
Html is minified: 109.03 %
0.250
E
Server: nginx/1.26.2
Date: Fri, 12 Dec 2025 21:27:10 GMT
Connection: keep-alive
Location: https://www.ooredoo.com/
Content-Type: text/html
Content-Length: 169

• http://www.ooredoo.com/
104.20.38.150
301
https://www.ooredoo.com/

0.024
A
Date: Fri, 12 Dec 2025 21:27:10 GMT
Connection: keep-alive
Location: https://www.ooredoo.com/
X-Content-Type-Options: nosniff
Vary: accept-encoding
Server: cloudflare
CF-RAY: 9ad04de37daee52f-TXL
Content-Length: 0

• http://www.ooredoo.com/
172.66.147.2
301
https://www.ooredoo.com/

0.026
A
Date: Fri, 12 Dec 2025 21:27:10 GMT
Connection: keep-alive
Location: https://www.ooredoo.com/
X-Content-Type-Options: nosniff
Vary: accept-encoding
Server: cloudflare
CF-RAY: 9ad04de3adacc758-TXL
Content-Length: 0

• https://ooredoo.com/
20.21.128.2
301
https://www.ooredoo.com/
Html is minified: 109.03 %
4.904
N
Certificate error: RemoteCertificateChainErrors
Server: nginx/1.26.2
Date: Fri, 12 Dec 2025 21:27:11 GMT
Connection: keep-alive
Location: https://www.ooredoo.com/
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Type: text/html
Content-Length: 169

• https://www.ooredoo.com/
104.20.38.150
-103


0.030
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• https://www.ooredoo.com/
172.66.147.2
-103


0.027
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• http://ooredoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
20.21.128.2
301
https://www.ooredoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 109.03 %
0.123
E
Visible Content:
Server: nginx/1.26.2
Date: Fri, 12 Dec 2025 21:27:17 GMT
Connection: keep-alive
Location: https://www.ooredoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Type: text/html
Content-Length: 169

• http://www.ooredoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
104.20.38.150 br used - 111021 / 415715 - 73.29 %
404

Html is minified: 136.81 %
1.554

Not Found
Visible Content:
Date: Fri, 12 Dec 2025 21:27:18 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Server: cloudflare
Pragma: no-cache
cf-edge-cache: cache,platform=wordpress
Cache-Control: must-revalidate, max-age=1800
Link: <https://www.ooredoo.com/wp-json/>; rel="https://api.w.org/"
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT
Access-Control-Max-Age: 3600
Access-Control-Allow-Headers: Content-Type,Authorization
Vary: accept-encoding
Set-Cookie: __cflb=02DiuDXfzJg8TE3deR2khQkM8wYyaWeXCeCcvGqfGCqQg; HttpOnly; SameSite=Lax; Path=/; Expires=Sat, 13 Dec 2025 20:27:18 GMT
cf-cache-status: MISS
X-Content-Type-Options: nosniff
CF-RAY: 9ad04e0f7d52e52f-TXL
Content-Type: text/html; charset=UTF-8
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Content-Encoding: br
Content-Length: 111021

• http://www.ooredoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
172.66.147.2 br used - 110288 / 415715 - 73.47 %
404

Html is minified: 136.81 %
0.067
A
Not Found
Visible Content:
Date: Fri, 12 Dec 2025 21:27:19 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Server: cloudflare
Pragma: no-cache
cf-edge-cache: cache,platform=wordpress
Cache-Control: must-revalidate, max-age=1800
Link: <https://www.ooredoo.com/wp-json/>; rel="https://api.w.org/"
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT
Access-Control-Max-Age: 3600
Access-Control-Allow-Headers: Content-Type,Authorization
X-Content-Type-Options: nosniff
Vary: accept-encoding
Age: 0
cf-cache-status: HIT
CF-RAY: 9ad04e1bc9a0c758-TXL
Content-Type: text/html; charset=UTF-8
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Content-Encoding: br
Content-Length: 110288

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

-103


0.030
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.
Visible Content:

• https://20.21.128.2/
20.21.128.2 gzip used - 114 / 153 - 25.49 %
404

Html is minified: 110.07 %
5.427
N
Not Found
Certificate error: RemoteCertificateNameMismatch
Server: nginx/1.26.2
Date: Fri, 12 Dec 2025 21:27:20 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Content-Type: text/html
Content-Encoding: gzip
Content-Length: 114

• https://172.66.147.2/
172.66.147.2
-103


0.023
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure'. (FF: SSL_ERROR_NO_CYPHER_OVERLAP)

• https://104.20.38.150/
104.20.38.150
-103


0.030
P
SecureConnectionError (3, 0x80131620). The SSL connection could not be established, see inner exception. Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

 

7. Comments


1. General Results, most used to calculate the result

Aname "ooredoo.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 108094 (complete: 276475)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: www.ooredoo.com has 2 different ip addresses (authoritative).
Warning: Only one ip address found: ooredoo.com 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: ooredoo.com 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.ooredoo.com has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
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):2 complete Content-Type - header (3 urls)
https://20.21.128.2/ 20.21.128.2


Url with incomplete Content-Type - header - missing charset
http://www.ooredoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.20.38.150
404
__cflb=02DiuDXfzJg8TE3deR2khQkM8wYyaWeXCeCcvGqfGCqQg; HttpOnly; SameSite=Lax; Path=/; Expires=Sat, 13 Dec 2025 20:27:18 GMT
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.
CError - no version with Http-Status 200
Ehttp://ooredoo.com/ 20.21.128.2
301
https://www.ooredoo.com/
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
Mhttps://20.21.128.2/ 20.21.128.2
404

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://ooredoo.com/ 20.21.128.2
301
https://www.ooredoo.com/
Error - Certificate isn't trusted, RemoteCertificateChainErrors
Nhttps://20.21.128.2/ 20.21.128.2
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.ooredoo.com, 2 ip addresses.
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain ooredoo.com, 1 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.ooredoo.com, 2 ip addresses.
BNo _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.ooredoo.com

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
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.dns1.qatar.net.qa (212.77.192.28), dns2.qatar.net.qa (212.77.192.30), dns3.qatar.net.qa (3.69.128.92)
AGood (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: dns1.qatar.net.qa, dns2.qatar.net.qa, dns3.qatar.net.qa, 3 Name Servers included in Delegation: dns1.qatar.net.qa, dns2.qatar.net.qa, dns3.qatar.net.qa, 3 Name Servers included in 1 Zone definitions: dns1.qatar.net.qa, dns2.qatar.net.qa, dns3.qatar.net.qa, 1 Name Servers listed in SOA.Primary: dns1.qatar.net.qa.
AGood: Only one SOA.Primary Name Server found.: dns1.qatar.net.qa.
AGood: SOA.Primary Name Server included in the delegation set.: dns1.qatar.net.qa.
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: dns1.qatar.net.qa, dns2.qatar.net.qa, dns3.qatar.net.qa
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: 3 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 3 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.: 3 Name Servers, 1 Top Level Domain: net.qa
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: qatar.net.qa
AGood: Name servers with different Country locations found: 3 Name Servers, 2 Countries: DE, QA
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 212., 3., 2 different subnets (first two Bytes): 212.77., 3.69., 2 different subnets (first three Bytes): 212.77.192., 3.69.128.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 3 good Nameserver
AGood: Nameserver supports Echo Capitalization: 3 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 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.

4. Content- and Performance-critical Checks

https://www.ooredoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-103

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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.
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
http://www.ooredoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.20.38.150
404
1.554 seconds
Warning: 404 needs more then one second
https://20.21.128.2/ 20.21.128.2
404
5.427 seconds
Warning: 404 needs more then one second
AInfo: Different Server-Headers found
ADuration: 179393 milliseconds, 179.393 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
ooredoo.com
20.21.128.2
443
Certificate/chain invalid
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok
ooredoo.com
20.21.128.2
443
Certificate/chain invalid
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - incomplete

1CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA


2CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US


20.21.128.2
20.21.128.2
443
name does not match
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
supported
ok

20.21.128.2
20.21.128.2
443
name does not match
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
supported
ok
http/2 via ALPN supported 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - incomplete

1CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA


2CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US

 

9. Certificates

1.
1.
CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA
27.10.2024
28.11.2025
78 days expired		www.ooredoo.com, ooredoo.com, staging.ooredoo.com, global.ooredoo.com, www.staging.ooredoo.com - 5 entries
1.
1.
CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA
27.10.2024

28.11.2025
78 days expired


www.ooredoo.com, ooredoo.com, staging.ooredoo.com, global.ooredoo.com, www.staging.ooredoo.com - 5 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0FAEAAB243C34E6C889A2EC16D5356A1
Thumbprint:66CCB0B6B88980E7B5F2F38D04A7CFA43C0AF533
SHA256 / Certificate:A5uC4eiFaQikm6Q/F9DAy5UPkhO5n1Dmx+U85SNxfGQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):d8c9c0ac41fc0fcc6fbf140c39d606bc3275996e0da1212b8d5864bc8b0cb269
SHA256 hex / Subject Public Key Information (SPKI):d8c9c0ac41fc0fcc6fbf140c39d606bc3275996e0da1212b8d5864bc8b0cb269 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.digicert.com
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)


NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.


2.
CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA
27.10.2024
28.11.2025
78 days expired		www.ooredoo.com, ooredoo.com, staging.ooredoo.com, global.ooredoo.com, www.staging.ooredoo.com - 5 entries

2.
CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA
27.10.2024

28.11.2025
78 days expired


www.ooredoo.com, ooredoo.com, staging.ooredoo.com, global.ooredoo.com, www.staging.ooredoo.com - 5 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0FAEAAB243C34E6C889A2EC16D5356A1
Thumbprint:66CCB0B6B88980E7B5F2F38D04A7CFA43C0AF533
SHA256 / Certificate:A5uC4eiFaQikm6Q/F9DAy5UPkhO5n1Dmx+U85SNxfGQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):d8c9c0ac41fc0fcc6fbf140c39d606bc3275996e0da1212b8d5864bc8b0cb269
SHA256 hex / Subject Public Key Information (SPKI):d8c9c0ac41fc0fcc6fbf140c39d606bc3275996e0da1212b8d5864bc8b0cb269 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.digicert.com
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)


NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.


3.
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
30.03.2021
30.03.2031
expires in 1870 days

3.
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
30.03.2021

30.03.2031
expires in 1870 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0CF5BD062B5602F47AB8502C23CCF066
Thumbprint:1B511ABEAD59C6CE207077C0BF0E0043B1382612
SHA256 / Certificate:yAJfn8Zf38lbPKjMeGe5pYe1J3lzlXkXRj/IE9C2Jak=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):59e738e674221702af1edb87c5200c1a4b75f64fae3d2c3d265124c61bd83c79
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




4.
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
30.03.2021
30.03.2031
expires in 1870 days

4.
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
30.03.2021

30.03.2031
expires in 1870 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0CF5BD062B5602F47AB8502C23CCF066
Thumbprint:1B511ABEAD59C6CE207077C0BF0E0043B1382612
SHA256 / Certificate:yAJfn8Zf38lbPKjMeGe5pYe1J3lzlXkXRj/IE9C2Jak=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):59e738e674221702af1edb87c5200c1a4b75f64fae3d2c3d265124c61bd83c79
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




5.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
29.10.2024
09.11.2031
expires in 2094 days

5.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
29.10.2024

09.11.2031
expires in 2094 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0E7D75235CA83761577F4CCD24CD6D1D
Thumbprint:B7402517EEAAC80AB04681186E8247BD7851CD0A
SHA256 / Certificate:oNYJp+PENOh4qaHBvQZbjc8zqn7+4bEbx1zOXloEIIA=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.cn
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




6.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
01.08.2013
15.01.2038
expires in 4353 days

6.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
01.08.2013

15.01.2038
expires in 4353 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:033AF1E6A711A9A0BB2864B11D09FAE5
Thumbprint:DF3C24F9BFD666761B268073FE06D1CC8D4F82A4
SHA256 / Certificate:yzzLt2Ax5eATj43TmiP53kf/w15DwRRM6ifUalqxy18=
SHA256 hex / Cert (DANE * 0 1):cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
SHA256 hex / PublicKey (DANE * 1 1):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
SHA256 hex / Subject Public Key Information (SPKI):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
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=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
10.11.2006
10.11.2031
expires in 2095 days

7.
CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
10.11.2006

10.11.2031
expires in 2095 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:02AC5C266A0B409B8F0B79F2AE462577
Thumbprint:5FB7EE0633E259DBAD0C4C9AE6D38F1A61C7DC25
SHA256 / Certificate:dDHl9MPBzkaQd08LYeBUQIg7qaAe0Aumq9eAbtOxGM8=
SHA256 hex / Cert (DANE * 0 1):7431e5f4c3c1ce4690774f0b61e05440883ba9a01ed00ba6abd7806ed3b118cf
SHA256 hex / PublicKey (DANE * 1 1):5a889647220e54d6bd8a16817224520bb5c78e58984bd570506388b9de0f075f
SHA256 hex / Subject Public Key Information (SPKI):5a889647220e54d6bd8a16817224520bb5c78e58984bd570506388b9de0f075f
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:




2.
1.
CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA
05.11.2025
02.12.2026
expires in 291 days		www.ooredoo.com, ooredoo.com, staging.ooredoo.com, global.ooredoo.com, www.staging.ooredoo.com - 5 entries
2.
1.
CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA
05.11.2025

02.12.2026
expires in 291 days


www.ooredoo.com, ooredoo.com, staging.ooredoo.com, global.ooredoo.com, www.staging.ooredoo.com - 5 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:056224324600E9C00E385595EFC82E98
Thumbprint:17AB51D0ADBFC18678073944E3A9D7B951CAEDA5
SHA256 / Certificate:Rk1SjaMwer/S8rja0oB2CU2mR3R4nI6ktn+Fu1+KbAo=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):d8c9c0ac41fc0fcc6fbf140c39d606bc3275996e0da1212b8d5864bc8b0cb269
SHA256 hex / Subject Public Key Information (SPKI):d8c9c0ac41fc0fcc6fbf140c39d606bc3275996e0da1212b8d5864bc8b0cb269 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




2.
CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA
05.11.2025
02.12.2026
expires in 291 days		www.ooredoo.com, ooredoo.com, staging.ooredoo.com, global.ooredoo.com, www.staging.ooredoo.com - 5 entries

2.
CN=www.ooredoo.com, O=Ooredoo Q. P.s.c, L=Doha, C=QA
05.11.2025

02.12.2026
expires in 291 days


www.ooredoo.com, ooredoo.com, staging.ooredoo.com, global.ooredoo.com, www.staging.ooredoo.com - 5 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:056224324600E9C00E385595EFC82E98
Thumbprint:17AB51D0ADBFC18678073944E3A9D7B951CAEDA5
SHA256 / Certificate:Rk1SjaMwer/S8rja0oB2CU2mR3R4nI6ktn+Fu1+KbAo=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):d8c9c0ac41fc0fcc6fbf140c39d606bc3275996e0da1212b8d5864bc8b0cb269
SHA256 hex / Subject Public Key Information (SPKI):d8c9c0ac41fc0fcc6fbf140c39d606bc3275996e0da1212b8d5864bc8b0cb269 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
30.03.2021
30.03.2031
expires in 1870 days

3.
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
30.03.2021

30.03.2031
expires in 1870 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0CF5BD062B5602F47AB8502C23CCF066
Thumbprint:1B511ABEAD59C6CE207077C0BF0E0043B1382612
SHA256 / Certificate:yAJfn8Zf38lbPKjMeGe5pYe1J3lzlXkXRj/IE9C2Jak=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):59e738e674221702af1edb87c5200c1a4b75f64fae3d2c3d265124c61bd83c79
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




4.
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
30.03.2021
30.03.2031
expires in 1870 days

4.
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
30.03.2021

30.03.2031
expires in 1870 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0CF5BD062B5602F47AB8502C23CCF066
Thumbprint:1B511ABEAD59C6CE207077C0BF0E0043B1382612
SHA256 / Certificate:yAJfn8Zf38lbPKjMeGe5pYe1J3lzlXkXRj/IE9C2Jak=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):59e738e674221702af1edb87c5200c1a4b75f64fae3d2c3d265124c61bd83c79
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




5.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
29.10.2024
09.11.2031
expires in 2094 days

5.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
29.10.2024

09.11.2031
expires in 2094 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0E7D75235CA83761577F4CCD24CD6D1D
Thumbprint:B7402517EEAAC80AB04681186E8247BD7851CD0A
SHA256 / Certificate:oNYJp+PENOh4qaHBvQZbjc8zqn7+4bEbx1zOXloEIIA=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.cn
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




6.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
01.08.2013
15.01.2038
expires in 4353 days

6.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
01.08.2013

15.01.2038
expires in 4353 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:033AF1E6A711A9A0BB2864B11D09FAE5
Thumbprint:DF3C24F9BFD666761B268073FE06D1CC8D4F82A4
SHA256 / Certificate:yzzLt2Ax5eATj43TmiP53kf/w15DwRRM6ifUalqxy18=
SHA256 hex / Cert (DANE * 0 1):cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
SHA256 hex / PublicKey (DANE * 1 1):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
SHA256 hex / Subject Public Key Information (SPKI):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
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=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
10.11.2006
10.11.2031
expires in 2095 days

7.
CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
10.11.2006

10.11.2031
expires in 2095 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:02AC5C266A0B409B8F0B79F2AE462577
Thumbprint:5FB7EE0633E259DBAD0C4C9AE6D38F1A61C7DC25
SHA256 / Certificate:dDHl9MPBzkaQd08LYeBUQIg7qaAe0Aumq9eAbtOxGM8=
SHA256 hex / Cert (DANE * 0 1):7431e5f4c3c1ce4690774f0b61e05440883ba9a01ed00ba6abd7806ed3b118cf
SHA256 hex / PublicKey (DANE * 1 1):5a889647220e54d6bd8a16817224520bb5c78e58984bd570506388b9de0f075f
SHA256 hex / Subject Public Key Information (SPKI):5a889647220e54d6bd8a16817224520bb5c78e58984bd570506388b9de0f075f
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=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
0
1
3
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
12579261725
precert		CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
2025-11-05 00:00:00
2026-12-01 23:59:59
global.ooredoo.com, ooredoo.com, staging.ooredoo.com, www.ooredoo.com, www.staging.ooredoo.com - 5 entries


8507200317
precert		CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
2024-10-27 00:00:00
2025-11-27 23:59:59
global.ooredoo.com, ooredoo.com, staging.ooredoo.com, www.ooredoo.com, www.staging.ooredoo.com - 5 entries


6029198020
leaf cert		CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
2023-10-18 00:00:00
2024-10-29 23:59:59
global.ooredoo.com, ooredoo.com, staging.ooredoo.com, www.ooredoo.com, www.staging.ooredoo.com - 5 entries


4235826510
precert		CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
2022-09-29 00:00:00
2023-10-30 23:59:59
global.ooredoo.com, ooredoo.com, staging.ooredoo.com, www.ooredoo.com, www.staging.ooredoo.com - 5 entries


 

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

Issuerlast 7 daysactivenum Certs
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
0
0
2
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
0
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
19512928885
leaf cert		CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
2024-10-26 22:00:00
2025-11-27 22:59:59
global.ooredoo.com, ooredoo.com, staging.ooredoo.com, www.ooredoo.com, www.staging.ooredoo.com
5 entries


12346736681
leaf cert		CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
2023-10-17 22:00:00
2024-10-29 22:59:59
global.ooredoo.com, ooredoo.com, staging.ooredoo.com, www.ooredoo.com, www.staging.ooredoo.com
5 entries


7640069351
precert		CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
2022-09-28 22:00:00
2023-10-30 22:59:59
global.ooredoo.com, ooredoo.com, staging.ooredoo.com, www.ooredoo.com, www.staging.ooredoo.com
5 entries


 

11. Html-Content - Entries

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

 

12. Html-Parsing via https://validator.w3.org/nu/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns1.qatar.net.qa, dns2.qatar.net.qa, dns3.qatar.net.qa

 

QNr.DomainTypeNS used
1
qa
NS
k.root-servers.net (2001:7fd::1)

Answer: a.registry.qa, b.registry.qa, c.registry.qa, d.registry.qa, e.registry.qa, f.registry.qa, g.registry.qa, h.registry.qa, i.registry.qa
2
dns1.qatar.net.qa: 212.77.192.28
NS
f.registry.qa (2001:dcd:1::6)

Answer: dns2.qatar.net.qa
212.77.192.30

Answer: dns3.qatar.net.qa
3.69.128.92

Answer: ns1.qatar.net.qa
212.77.192.10

Answer: ns2.qatar.net.qa
212.77.192.13

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.ooredoo.com.cdn.cloudflare.net
0

no CAA entry found
1
0
ooredoo.com.cdn.cloudflare.net
0

no CAA entry found
1
0
com.cdn.cloudflare.net
0

no CAA entry found
1
0
cdn.cloudflare.net
0

no CAA entry found
1
0
www.ooredoo.com



1
0
cloudflare.net
0

no CAA entry found
1
0
ooredoo.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
ooredoo.com
_i084dperqyyity97ovp0c0eduvk74dp
ok
1
0
ooredoo.com
67vqd36yl27k7ng1vmkql4rr7v42mhh9
ok
1
0
ooredoo.com
6vxZ2pPNtVFrqFT8ww5u4yWVMa461pdaA5DcT+S1cfLlECF5eeWFevUQHBoEO+VvywTmJoxkHupi/j+0RLAs5w==
ok
1
0
ooredoo.com
qw6k02q211cz1xmh1k99q27h1q2b741b
ok
1
0
ooredoo.com
v=spf1 mx ip4:86.62.246.44 ip4:86.62.246.43 ip4:203.41.57.145 ip4:212.77.206.2 ip4:86.62.247.184 ip4:86.62.246.55 ip4:213.130.113.73 ip4:86.62.246.126 include:spf.protection.outlook.com -all
ok
1
0
www.ooredoo.com


1
0
_acme-challenge.ooredoo.com

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

Name Error - The domain name does not exist
1
0
www.ooredoo.com.cdn.cloudflare.net

ok
1
0
_acme-challenge.ooredoo.com.ooredoo.com

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

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

Name Error - The domain name does not exist
1
0
_acme-challenge.www.ooredoo.com.cdn.cloudflare.net

missing entry or wrong length
1
0
_acme-challenge.www.ooredoo.com.cdn.cloudflare.net.ooredoo.com.cdn.cloudflare.net

 perhaps wrong
1
0
_acme-challenge.www.ooredoo.com.cdn.cloudflare.net.www.ooredoo.com.cdn.cloudflare.net

 perhaps wrong
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

ooredoo.com
5
jupiter.ooredoo.qa
02ok

A


86.62.246.126
01ok

CNAME


00ok
MX

ooredoo.com
5
mercury.ooredoo.qa
02ok

A


213.130.113.73
01ok

CNAME


00ok
SPF
TXT
ooredoo.com

v=spf1 mx ip4:86.62.246.44 ip4:86.62.246.43 ip4:203.41.57.145 ip4:212.77.206.2 ip4:86.62.247.184 ip4:86.62.246.55 ip4:213.130.113.73 ip4:86.62.246.126 include:spf.protection.outlook.com -all
ok

MX
ooredoo.com

jupiter.ooredoo.qa
ok

MX-A
jupiter.ooredoo.qa

86.62.246.126
8192Duplicated ipv4 found.

MX
ooredoo.com

mercury.ooredoo.qa
ok

MX-A
mercury.ooredoo.qa

213.130.113.73
8192Duplicated ipv4 found.

TXT
ooredoo.com

ip4:213.130.113.73
8192Duplicated ipv4 found.

TXT
ooredoo.com

ip4:86.62.246.126
8192Duplicated ipv4 found.

TXT
spf.protection.outlook.com

v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all
ok
_dmarc
TXT
_dmarc.ooredoo.com

v=DMARC1; p=quarantine; rua=mailto:dmarc@ooredoo.qa; ruf=mailto:dmarc@ooredoo.qa; fo=1
ok

TXT
ooredoo.com._report._dmarc.ooredoo.qa

mailto:dmarc@ooredoo.qa
okMail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.

TXT
ooredoo.com._report._dmarc.ooredoo.qa

v=DMARC1
okConfirmed. Sending reports to external domain is allowed.

				 
			

				 
			
17. Cipher Suites



Skipped, CDN used or too many ip addresses

				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=2128f93d-c04a-480b-add8-e9d831033420

				 
			


Last Result: https://check-your-website.server-daten.de/?q=ooredoo.com - 2025-12-12 22:24:39

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

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

				 
			

				 
			


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

				 
			
QR-Code of this page - https://check-your-website.server-daten.de/?d=ooredoo.com

				 
			

				 
			



Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • 
USt-IdNr.: DE221734518

				 
			


Errors, ideas, questions? Use the 
Contact form • A project using

Server-Daten - Web Database solutions