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





1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
ooredoo.tn
A
196.203.59.19
Aryanah/Ariana Governorate/Tunisia (TN) - Ooredoo-Tunisia
Hostname: ooredoo.tn
yes
1
0

AAAA
2c0f:f698:f00a::1
Tunis/Tunis Governorate/Tunisia (TN) - Ooredoo Tunisie SA

yes


www.ooredoo.tn
A
196.203.59.19
Aryanah/Ariana Governorate/Tunisia (TN) - Ooredoo-Tunisia
Hostname: ooredoo.tn
yes
1
0

AAAA
2c0f:f698:f00a::1
Tunis/Tunis Governorate/Tunisia (TN) - Ooredoo Tunisie SA

yes


*.ooredoo.tn
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 5613, Flags 256



Public Key with Algorithm 8, KeyTag 20038, 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: 22.07.2024, 00:00:00 +, Signature-Inception: 01.07.2024, 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: tn
tn
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 8629, DigestType 2 and Digest BciRMD/e5P2uJY4qfUg3DOIfmAWMDuClDEOMKHio4tY=



1 RRSIG RR to validate DS RR found



RRSIG-Owner tn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.07.2024, 05:00:00 +, Signature-Inception: 10.07.2024, 04:00:00 +, KeyTag 20038, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 36171, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner tn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.07.2024, 19:53:46 +, Signature-Inception: 09.07.2024, 19:35:17 +, KeyTag 8629, Signer-Name: tn



RRSIG-Owner tn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.07.2024, 19:53:46 +, Signature-Inception: 09.07.2024, 19:35:17 +, KeyTag 36171, Signer-Name: tn



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 8629 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 36171 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 8629, DigestType 2 and Digest "BciRMD/e5P2uJY4qfUg3DOIfmAWMDuClDEOMKHio4tY=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: ooredoo.tn
ooredoo.tn
2 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 7481, DigestType 2 and Digest /9fpKjqm4P+feFWMy8wYo4uSX0vK521MK1iUavAe68M=



DS with Algorithm 13, KeyTag 7481, DigestType 4 and Digest Hpqi3r1r5Lh+EGkJVUAzspjhN+90z8vFbgwhSBqB3XhrJWvAvJ9Sm+NauJOpijEo



1 RRSIG RR to validate DS RR found



RRSIG-Owner ooredoo.tn., Algorithm: 8, 2 Labels, original TTL: 60 sec, Signature-expiration: 24.07.2024, 20:43:02 +, Signature-Inception: 09.07.2024, 20:17:59 +, KeyTag 36171, Signer-Name: tn



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



1 DNSKEY RR found



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



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



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 7481, DigestType 2 and Digest "/9fpKjqm4P+feFWMy8wYo4uSX0vK521MK1iUavAe68M=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 7481, DigestType 4 and Digest "Hpqi3r1r5Lh+EGkJVUAzspjhN+90z8vFbgwhSBqB3XhrJWvAvJ9Sm+NauJOpijEo" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



RRSIG Type 1 validates the A - Result: 196.203.59.19
Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



RRSIG Type 16 validates the TXT - Result: ms25975949 MS=ms25975949 MS=ms47630306 MS=ms65053947 MS=ms86534095 v=spf1 include:_spf.ooredoo.tn -all google-site-verification=AKyt4Nulsy1-JtSbnu2V0Vitvn4cgx5NVeAR9NjG8KY csdwn4++E89TNYwNfikkKN2WEr2suv7OUXkNPO+4pn6Vxo9exNS+iRtKlH9aKT3W7pisiohZaqp5XfnFrGZfCA==
Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



RRSIG Type 28 validates the AAAA - Result: 2C0F:F698:F00A:0000:0000:0000:0000:0001
Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 60 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



CNAME-Query sends a valid NSEC RR as result with the query name "ooredoo.tn" equal the NSEC-owner "ooredoo.tn" and the NextOwner "100seconds.ooredoo.tn". 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, NS, SOA, MX, TXT, AAAA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.ooredoo.tn) sends a valid NSEC RR as result with the owner name ooredoo.tn. 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 "ooredoo.tn" and the NextOwner "100seconds.ooredoo.tn". So that NSEC confirms the not-existence of the Wildcard expansion.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



Status: Good. NXDomain-Proof required and found.



TLSA-Query (_443._tcp.ooredoo.tn) sends a valid NSEC RR as result with the query name "_443._tcp.ooredoo.tn" between the NSEC-owner "_spf.ooredoo.tn" and the NextOwner "_collab-edge._tls.ooredoo.tn". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.ooredoo.tn) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.ooredoo.tn" between the NSEC-owner "_spf.ooredoo.tn" and the NextOwner "_collab-edge._tls.ooredoo.tn". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _spf.ooredoo.tn., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "ooredoo.tn" equal the NSEC-owner "ooredoo.tn" and the NextOwner "100seconds.ooredoo.tn". 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, NS, SOA, MX, TXT, AAAA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



Status: Good. NoData-Proof required and found.

Zone: www.ooredoo.tn
www.ooredoo.tn
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.tn" and the NextOwner "yprov-phone-services.ooredoo.tn". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, AAAA, RRSIG, NSEC



RRSIG Type 1 validates the A - Result: 196.203.59.19
Validated: RRSIG-Owner www.ooredoo.tn., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



RRSIG Type 28 validates the AAAA - Result: 2C0F:F698:F00A:0000:0000:0000:0000:0001
Validated: RRSIG-Owner www.ooredoo.tn., Algorithm: 13, 3 Labels, original TTL: 60 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



CNAME-Query sends a valid NSEC RR as result with the query name "www.ooredoo.tn" equal the NSEC-owner "www.ooredoo.tn" and the NextOwner "yprov-phone-services.ooredoo.tn". 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, AAAA, RRSIG, NSEC Validated: RRSIG-Owner www.ooredoo.tn., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC RR as result with the query name "www.ooredoo.tn" equal the NSEC-owner "www.ooredoo.tn" and the NextOwner "yprov-phone-services.ooredoo.tn". 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, AAAA, RRSIG, NSEC Validated: RRSIG-Owner www.ooredoo.tn., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.www.ooredoo.tn) sends a valid NSEC RR as result with the owner name www.ooredoo.tn. 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 "www.ooredoo.tn" and the NextOwner "yprov-phone-services.ooredoo.tn". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.www.ooredoo.tn) sends a valid NSEC RR as result with the query name "_443._tcp.www.ooredoo.tn" between the NSEC-owner "www.ooredoo.tn" and the NextOwner "yprov-phone-services.ooredoo.tn". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.www.ooredoo.tn) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.www.ooredoo.tn" between the NSEC-owner "www.ooredoo.tn" and the NextOwner "yprov-phone-services.ooredoo.tn". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: A, AAAA, RRSIG, NSEC Validated: RRSIG-Owner www.ooredoo.tn., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "www.ooredoo.tn" equal the NSEC-owner "www.ooredoo.tn" and the NextOwner "yprov-phone-services.ooredoo.tn". 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, AAAA, RRSIG, NSEC Validated: RRSIG-Owner www.ooredoo.tn., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn



Status: Good. NoData-Proof required and found.


3. Name Servers

DomainNameserverNS-IP
www.ooredoo.tn
  ns1.ooredoo.tn / vmsecdns

ooredoo.tn
  ns1.ooredoo.tn / vmsecdns
196.203.59.53
Aryanah/Ariana Governorate/Tunisia (TN) - Ooredoo-Tunisia


  ns2.ooredoo.tn / vmsecdnsmgh
196.203.58.53
Tunis/Tunis Governorate/Tunisia (TN) - Ooredoo-Tunisia


  ns3.ooredoo.tn / ns
41.228.41.200
Tunis/Tunis Governorate/Tunisia (TN) - Ooredoo-Tunisia

tn
  ns1.ati.tn / BNS51


  ns2.ati.tn / KNS53


  ns2.nic.fr / ns2.th2.nic.fr


  ns-tn.afrinic.net / s01-ns2.pkl


  pch.ati.tn / 2.ams.pch


  rip.psg.com / rip.psg.com


4. SOA-Entries


Domain:tn
Zone-Name:tn
Primary:ns1.ati.tn
Mail:hostmaster.ati.tn
Serial:2024159170
Refresh:21600
Retry:10800
Expire:604800
TTL:86400
num Entries:6


Domain:ooredoo.tn
Zone-Name:ooredoo.tn
Primary:ns1.ooredoo.tn
Mail:admin.ooredoo.tn
Serial:2024071002
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
num Entries:3


Domain:www.ooredoo.tn
Zone-Name:ooredoo.tn
Primary:ns1.ooredoo.tn
Mail:admin.ooredoo.tn
Serial:2024071002
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
num Entries:1


5. Screenshots

Startaddress: https://www.ooredoo.tn/Personal/en/accueil, address used: https://www.ooredoo.tn/Personal/en/accueil, Screenshot created 2023-05-15 15:37:52 +00:0 url is insecure, certificate invalid

Mobil (412px x 732px)

3805 milliseconds

Screenshot mobile - https://www.ooredoo.tn/Personal/en/accueil
Mobil + Landscape (732px x 412px)

5290 milliseconds

Screenshot mobile landscape - https://www.ooredoo.tn/Personal/en/accueil
Screen (1280px x 1680px)

7439 milliseconds

Screenshot Desktop - https://www.ooredoo.tn/Personal/en/accueil

Mobile- and other Chrome-Checks

widthheight
visual Viewport412732
content Size4124402

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

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://ooredoo.tn/
196.203.59.19
302
https://ooredoo.tn/
0.130
A
Location: https://ooredoo.tn/
Connection: close
Content-Length: 0

• http://www.ooredoo.tn/
196.203.59.19
302
https://www.ooredoo.tn/
0.130
A
Location: https://www.ooredoo.tn/
Connection: close
Content-Length: 0

• http://ooredoo.tn/
2c0f:f698:f00a::1
-14

10.013
T
Timeout - The operation has timed out.

• http://www.ooredoo.tn/
2c0f:f698:f00a::1
-14

10.010
T
Timeout - The operation has timed out.

• https://ooredoo.tn/
196.203.59.19
301
http://www.ooredoo.tn/
Html is minified: 100.00 %
4.033
F
Date: Wed, 10 Jul 2024 10:31:07 GMT
Location: http://www.ooredoo.tn/
Connection: close
Set-Cookie: TS019bcb7f=01e05c51dbb0d335ce6c2b02ba65f97a52fa1589ec42cf28300e56c45a727e731ffa590dd3d9ab8c9cb229caa9a45b953844b62cfe; Path=/; Domain=.ooredoo.tn; Secure; Httponly, TS9792adba029=08bfb15f6aab2800ce389b83f966237e73fe639132bc96256bbcfd261f4e1599ff42fc8bd9ad9cb3844c29e577660a9e; Max-Age=30; Path=/; Secure; Httponly
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=16070400; includeSubDomains
Content-Length: 230
Content-Type: text/html; charset=iso-8859-1

• https://www.ooredoo.tn/
196.203.59.19
302
https://www.ooredoo.tn/personal/accueil
4.167
B
Date: Wed, 10 Jul 2024 10:31:22 GMT
Location: https://www.ooredoo.tn/personal/accueil
Connection: close
Set-Cookie: TS0138d5e7=01e05c51db3f502a215ddad0a670692f3d5efa43f40c8273495f0281c941db4d41518dcbd90dc1315f374468207dc6c60698a92ea7; Path=/; Domain=.www.ooredoo.tn; Secure; Httponly, TS9792adba029=08bfb15f6aab28001944db0cc11af514b51846ed3fcefd4cc9f593dd1df046d2b6ddc4394d06ccbcf6d08275634b4b85; Max-Age=30; Path=/; Secure; Httponly
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=16070400; includeSubDomains
Content-Length: 0
Content-Type: text/html; charset=utf-8

• https://ooredoo.tn/
2c0f:f698:f00a::1
-14

10.006
T
Timeout - The operation has timed out.

• https://www.ooredoo.tn/
2c0f:f698:f00a::1
-14

10.013
T
Timeout - The operation has timed out.

• https://www.ooredoo.tn/personal/accueil

-14

10.010
T
Timeout - The operation has timed out.

• http://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
196.203.59.19
302
https://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.143
A
Visible Content:
Location: https://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Connection: close
Content-Length: 0

• http://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
196.203.59.19
302
https://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.137
A
Visible Content:
Location: https://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Connection: close
Content-Length: 0

• http://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2c0f:f698:f00a::1
-14

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

• http://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2c0f:f698:f00a::1
-14

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

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

-14

10.013
T
Timeout - The operation has timed out.
Visible Content:

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

-14

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

• https://196.203.59.19/
196.203.59.19
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 100.00 %
3.780
N
Certificate error: RemoteCertificateNameMismatch
Cache-Control: no-cache
Connection: close
Pragma: no-cache
Set-Cookie: TS9792adba029=08bfb15f6aab28006c438fa23287b6d2748c590c93b29df93a3c166bc21c0da995f511bd99807300c1e17065d61a5d4b; Max-Age=30; Path=/; Secure; Httponly
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=16070400; includeSubDomains
Content-Type: text/html; charset=utf-8
Content-Length: 109

• https://[2c0f:f698:f00a:0000:0000:0000:0000:0001]/
2c0f:f698:f00a::1
-14

10.013
T
Timeout - The operation has timed out.

7. Comments


1. General Results, most used to calculate the result

Aname "ooredoo.tn" is domain, public suffix is ".tn", top-level-domain is ".tn", top-level-domain-type is "country-code", Country is Tunisia, tld-manager is "Agence Tunisienne d'Internet", num .tn-domains preloaded: 34 (complete: 245733)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: ooredoo.tn has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.ooredoo.tn has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: ooredoo.tn has 1 ipv4, 1 ipv6 addresses
AGood: Ipv4 and Ipv6 addresses per domain name found: www.ooredoo.tn has 1 ipv4, 1 ipv6 addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: destination is https
AGood: No cookie sent via http.
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://ooredoo.tn/ 196.203.59.19
302
https://ooredoo.tn/
Correct redirect http - https with the same domain name
Ahttp://www.ooredoo.tn/ 196.203.59.19
302
https://www.ooredoo.tn/
Correct redirect http - https with the same domain name
BWarning: HSTS max-age is too short - minimum 31536000 = 365 days required, 16070400 seconds = 186 days found
Bhttps://ooredoo.tn/ 196.203.59.19
301
TS019bcb7f=01e05c51dbb0d335ce6c2b02ba65f97a52fa1589ec42cf28300e56c45a727e731ffa590dd3d9ab8c9cb229caa9a45b953844b62cfe; Path=/; Domain=.ooredoo.tn; 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://ooredoo.tn/ 196.203.59.19
301
TS9792adba029=08bfb15f6aab2800ce389b83f966237e73fe639132bc96256bbcfd261f4e1599ff42fc8bd9ad9cb3844c29e577660a9e; Max-Age=30; 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://www.ooredoo.tn/ 196.203.59.19
302
TS0138d5e7=01e05c51db3f502a215ddad0a670692f3d5efa43f40c8273495f0281c941db4d41518dcbd90dc1315f374468207dc6c60698a92ea7; Path=/; Domain=.www.ooredoo.tn; 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://www.ooredoo.tn/ 196.203.59.19
302
TS9792adba029=08bfb15f6aab28001944db0cc11af514b51846ed3fcefd4cc9f593dd1df046d2b6ddc4394d06ccbcf6d08275634b4b85; Max-Age=30; 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://196.203.59.19/ 196.203.59.19
200
TS9792adba029=08bfb15f6aab28006c438fa23287b6d2748c590c93b29df93a3c166bc21c0da995f511bd99807300c1e17065d61a5d4b; Max-Age=30; 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://ooredoo.tn/ 196.203.59.19
301
http://www.ooredoo.tn/
Wrong redirect https - http - never redirect https to http
Khttp://ooredoo.tn/ 196.203.59.19, Status 302

http://ooredoo.tn/ 2c0f:f698:f00a::1, Status -14
Configuration problem - different ip addresses with different status
Khttp://www.ooredoo.tn/ 196.203.59.19, Status 302

http://www.ooredoo.tn/ 2c0f:f698:f00a::1, Status -14
Configuration problem - different ip addresses with different status
Khttps://ooredoo.tn/ 196.203.59.19, Status 301

https://ooredoo.tn/ 2c0f:f698:f00a::1, Status -14
Configuration problem - different ip addresses with different status
Khttps://www.ooredoo.tn/ 196.203.59.19, Status 302

https://www.ooredoo.tn/ 2c0f:f698:f00a::1, Status -14
Configuration problem - different ip addresses with different status
Khttp://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 196.203.59.19, Status 302

http://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2c0f:f698:f00a::1, Status -14
Configuration problem - different ip addresses with different status
Khttp://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 196.203.59.19, Status 302

http://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2c0f:f698:f00a::1, Status -14
Configuration problem - different ip addresses with different status
Nhttps://196.203.59.19/ 196.203.59.19
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Oooredoo.tn / 196.203.59.19 / 443


Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 8 Cipher Suites without Forward Secrecy found
Owww.ooredoo.tn / 196.203.59.19 / 443


Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 8 Cipher Suites without Forward Secrecy found
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain ooredoo.tn, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.ooredoo.tn, 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.tn

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

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.ns1.ooredoo.tn (196.203.59.53, 2c0f:f698:f00a::53), ns2.ooredoo.tn (196.203.58.53), ns3.ooredoo.tn (41.228.41.200)
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: ns1.ooredoo.tn, ns2.ooredoo.tn, ns3.ooredoo.tn, 3 Name Servers included in Delegation: ns1.ooredoo.tn, ns2.ooredoo.tn, ns3.ooredoo.tn, 3 Name Servers included in 1 Zone definitions: ns1.ooredoo.tn, ns2.ooredoo.tn, ns3.ooredoo.tn, 1 Name Servers listed in SOA.Primary: ns1.ooredoo.tn.
AGood: Only one SOA.Primary Name Server found.: ns1.ooredoo.tn.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.ooredoo.tn.
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.ooredoo.tn, ns2.ooredoo.tn, ns3.ooredoo.tn
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: tn
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: ooredoo.tn
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: TN
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 196., 41., 2 different subnets (first two Bytes): 196.203., 41.228., 3 different subnets (first three Bytes): 196.203.58., 196.203.59., 41.228.41.
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: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 3 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns2.nic.fr: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns2.th2.nic.fr). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: rip.psg.com: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (rip.psg.com). COOKIE: fatal timeout. CLIENTSUBNET: ok.
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

http://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2c0f:f698:f00a::1
-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.
http://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2c0f:f698:f00a::1
-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.
https://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-14

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

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2c0f:f698:f00a::1, Status -14

http://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 196.203.59.19, Status 302
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2c0f:f698:f00a::1, Status -14

http://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 196.203.59.19, Status 302
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: No https + http status 200 with inline CSS / JavaScript found
AGood: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
https://196.203.59.19/ 196.203.59.19
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
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: 1054624 milliseconds, 1054.624 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
ooredoo.tn
196.203.59.19
443
ok
Tls12
ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok
ooredoo.tn
196.203.59.19
443
ok
Tls12

ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - incomplete
1CN=*.ooredoo.tn

2CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester


www.ooredoo.tn
196.203.59.19
443
ok
Tls12
ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok

www.ooredoo.tn
196.203.59.19
443
ok
Tls12

ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - incomplete
1CN=*.ooredoo.tn

2CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester


196.203.59.19
196.203.59.19
443
name does not match
Tls12
ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok

196.203.59.19
196.203.59.19
443
name does not match
Tls12

ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - incomplete
1CN=*.ooredoo.tn

2CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester


9. Certificates

1.
1.
CN=*.ooredoo.tn
08.11.2023
09.12.2024
expires in 149 days
*.ooredoo.tn, ooredoo.tn - 2 entries
1.
1.
CN=*.ooredoo.tn
08.11.2023

09.12.2024
expires in 149 days
*.ooredoo.tn, ooredoo.tn - 2 entries

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00EE5E8F5F9261648294DEFC8169F31446
Thumbprint:22529579C8C3E3178C4FC23B34D93F33E76AD3E1
SHA256 / Certificate:TkM0oHwOoTtWEsaXXha9BAn+1gh5rtGYkZJuJ307F5c=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):97aed2ad890347bd621358ced776b3d3e5a301eb95f628f41c93bff65e67c831
SHA256 hex / Subject Public Key Information (SPKI):97aed2ad890347bd621358ced776b3d3e5a301eb95f628f41c93bff65e67c831 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.sectigo.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)


2.
CN=*.ooredoo.tn
08.11.2023
09.12.2024
expires in 149 days
*.ooredoo.tn, ooredoo.tn - 2 entries

2.
CN=*.ooredoo.tn
08.11.2023

09.12.2024
expires in 149 days
*.ooredoo.tn, ooredoo.tn - 2 entries

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00EE5E8F5F9261648294DEFC8169F31446
Thumbprint:22529579C8C3E3178C4FC23B34D93F33E76AD3E1
SHA256 / Certificate:TkM0oHwOoTtWEsaXXha9BAn+1gh5rtGYkZJuJ307F5c=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):97aed2ad890347bd621358ced776b3d3e5a301eb95f628f41c93bff65e67c831
SHA256 hex / Subject Public Key Information (SPKI):97aed2ad890347bd621358ced776b3d3e5a301eb95f628f41c93bff65e67c831 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.sectigo.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)


3.
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, S=Greater Manchester, C=GB
02.11.2018
01.01.2031
expires in 2363 days


3.
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, S=Greater Manchester, C=GB
02.11.2018

01.01.2031
expires in 2363 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA384 With RSA Encryption
Serial Number:7D5B5126B476BA11DB74160BBC530DA7
Thumbprint:33E4E80807204C2B6182A3A14B591ACD25B5F0DB
SHA256 / Certificate:f6T/aOwEqZ11KNUIX5SQf00d0cU4G6zcgy7VyWAhRnY=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):e1ae9c3de848ece1ba72e0d991ae4d0d9ec547c6bad1dddab9d6beb0a7e0e0d8
SHA256 hex / Subject Public Key Information (SPKI):e1ae9c3de848ece1ba72e0d991ae4d0d9ec547c6bad1dddab9d6beb0a7e0e0d8
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.usertrust.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=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, S=Greater Manchester, C=GB
02.11.2018
01.01.2031
expires in 2363 days


4.
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, S=Greater Manchester, C=GB
02.11.2018

01.01.2031
expires in 2363 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA384 With RSA Encryption
Serial Number:7D5B5126B476BA11DB74160BBC530DA7
Thumbprint:33E4E80807204C2B6182A3A14B591ACD25B5F0DB
SHA256 / Certificate:f6T/aOwEqZ11KNUIX5SQf00d0cU4G6zcgy7VyWAhRnY=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):e1ae9c3de848ece1ba72e0d991ae4d0d9ec547c6bad1dddab9d6beb0a7e0e0d8
SHA256 hex / Subject Public Key Information (SPKI):e1ae9c3de848ece1ba72e0d991ae4d0d9ec547c6bad1dddab9d6beb0a7e0e0d8
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.usertrust.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=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US
01.02.2010
19.01.2038
expires in 4938 days


5.
CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US
01.02.2010

19.01.2038
expires in 4938 days


KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA384 With RSA Encryption
Serial Number:01FD6D30FCA3CA51A81BBC640E35032D
Thumbprint:2B8F1B57330DBBA2D07A6C51F70EE90DDAB9AD8E
SHA256 / Certificate:55PJsC/YqhPiHDEiisywgRlkO3SciYlksXRtRsPUy9I=
SHA256 hex / Cert (DANE * 0 1):e793c9b02fd8aa13e21c31228accb08119643b749c898964b1746d46c3d4cbd2
SHA256 hex / PublicKey (DANE * 1 1):c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SHA256 hex / Subject Public Key Information (SPKI):c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
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:



6.
CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US
12.03.2019
01.01.2029
expires in 1633 days


6.
CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US
12.03.2019

01.01.2029
expires in 1633 days


KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA384 With RSA Encryption
Serial Number:3972443AF922B751D7D36C10DD313595
Thumbprint:D89E3BD43D5D909B47A18977AA9D5CE36CEE184C
SHA256 / Certificate:aLnHYSGaWx8BMXhEdGZdthu9sQngDwXKn3QkTuX19Ss=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SHA256 hex / Subject Public Key Information (SPKI):c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.comodoca.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


7.
CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, S=Greater Manchester, C=GB
01.01.2004
01.01.2029
expires in 1633 days


7.
CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, S=Greater Manchester, C=GB
01.01.2004

01.01.2029
expires in 1633 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:01
Thumbprint:D1EB23A46D17D68FD92564C2F1F1601764D8E349
SHA256 / Certificate:16eg+11+JzHXcelITrze9x1fDD4KKUh4K8g+4OppnvQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):bd153ed7b0434f6886b17bce8bbe84ed340c7132d702a8f4fa318f756ecbd6f3
SHA256 hex / Subject Public Key Information (SPKI):bd153ed7b0434f6886b17bce8bbe84ed340c7132d702a8f4fa318f756ecbd6f3
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=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
1
2
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6150435487
leaf cert
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2023-11-08 00:00:00
2024-12-08 23:59:59
*.ooredoo.tn, ooredoo.tn - 2 entries


4340307886
leaf cert
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2022-10-25 00:00:00
2023-11-25 23:59:59
*.ooredoo.tn, ooredoo.tn - 2 entries


3897853384
precert
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
2022-06-30 00:00:00
2023-07-31 23:59:59
*.ooredoo.tn, ooredoo.tn - 2 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=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
1
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
11036839690
leaf cert
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2023-11-07 23:00:00
2024-12-08 22:59:59
*.ooredoo.tn, ooredoo.tn
2 entries


7831137300
precert
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2022-10-24 22:00:00
2023-11-25 22:59:59
*.ooredoo.tn, ooredoo.tn
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.ooredoo.tn, ns2.ooredoo.tn, ns3.ooredoo.tn

QNr.DomainTypeNS used
1
tn
NS
h.root-servers.net (2001:500:1::53)

Answer: ns-tn.afrinic.net, ns1.ati.tn, ns2.ati.tn, ns2.nic.fr, pch.ati.tn, rip.psg.com
2
ns1.ooredoo.tn: 196.203.59.53, 2c0f:f698:f00a::53
NS
ns-tn.afrinic.net (2001:43f8:120::25)

Answer: ns2.ooredoo.tn
196.203.58.53

Answer: ns3.ooredoo.tn
41.228.41.200


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.ooredoo.tn
0

no CAA entry found
1
0
ooredoo.tn
0

no CAA entry found
1
0
tn
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
ooredoo.tn
csdwn4++E89TNYwNfikkKN2WEr2suv7OUXkNPO+4pn6Vxo9exNS+iRtKlH9aKT3W7pisiohZaqp5XfnFrGZfCA==
ok
1
0
ooredoo.tn
google-site-verification=AKyt4Nulsy1-JtSbnu2V0Vitvn4cgx5NVeAR9NjG8KY
ok
1
0
ooredoo.tn
MS=ms25975949
ok
1
0
ooredoo.tn
MS=ms47630306
ok
1
0
ooredoo.tn
MS=ms65053947
ok
1
0
ooredoo.tn
MS=ms86534095
ok
1
0
ooredoo.tn
ms25975949
ok
1
0
ooredoo.tn
v=spf1 include:_spf.ooredoo.tn -all
ok
1
0
www.ooredoo.tn

ok
1
0
_acme-challenge.ooredoo.tn

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

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

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

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

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SPF-Check is alpha - 2024-06-22, DMARC-Detailcheck is alpha - 2024-07-06)

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

ooredoo.tn
5
corpas1.ooredoo.tn
02ok

A


196.203.59.112
01ok

CNAME


00ok
MX

ooredoo.tn
5
corpas2.ooredoo.tn
02ok

A


196.203.59.113
01ok

CNAME


00ok
SPF
TXT
ooredoo.tn

v=spf1 include:_spf.ooredoo.tn -all
ok

TXT
_spf.ooredoo.tn

v=spf1 include:_netblocks.ooredoo.tn include:_netblocks2.ooredoo.tn -all
ok

TXT
_netblocks.ooredoo.tn

v=spf1 ip4:196.203.59.118 ip4:196.203.59.119 -all
ok

TXT
_netblocks2.ooredoo.tn

v=spf1 ip4:154.72.229.13 ip4:154.72.229.12 -all
ok
_dmarc
TXT
_dmarc.ooredoo.tn

v=DMARC1; p=reject; rua=mailto:hknmjho3rg@rua.powerdmarc.com; ruf=mailto:hknmjho3rg@ruf.powerdmarc.com; pct=100; fo=1;
ok

TXT
ooredoo.tn._report._dmarc.rua.powerdmarc.com

mailto:hknmjho3rg@rua.powerdmarc.com
okMail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.

TXT
ooredoo.tn._report._dmarc.rua.powerdmarc.com

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

TXT
ooredoo.tn._report._dmarc.ruf.powerdmarc.com

mailto:hknmjho3rg@ruf.powerdmarc.com
okMail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.

TXT
ooredoo.tn._report._dmarc.ruf.powerdmarc.com

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



16. Cipher Suites

Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
ooredoo.tn
196.203.59.19
443
15 Ciphers84.98 sec
8 without, 7 FS
46.67 %
www.ooredoo.tn
196.203.59.19
443
15 Ciphers82.18 sec
8 without, 7 FS
46.67 %
Complete

2
30 Ciphers
15.00 Ciphers/Check
167.17 sec83.58 sec/Check
16 without, 14 FS
46.67 %

Details
DomainIPPortCipher (OpenSsl / IANA)
ooredoo.tn
196.203.59.19
443
ECDHE-RSA-CHACHA20-POLY1305
(Secure)
TLSv1.2
0xCC,0xA8
FS
15 Ciphers, 84.98 sec
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
ECDH
RSA
CHACHA20/POLY1305(256)
AEAD



ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
ECDH
RSA
AESGCM(256)
AEAD



ECDHE-RSA-AES128-GCM-SHA256
(Secure)
TLSv1.2
0xC0,0x2F
FS

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
ECDH
RSA
AESGCM(128)
AEAD



ECDHE-RSA-AES256-SHA384
(Weak)
TLSv1.2
0xC0,0x28
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
ECDH
RSA
AES(256)
SHA384



AES256-GCM-SHA384
(Weak)
TLSv1.2
0x00,0x9D
No FS

TLS_RSA_WITH_AES_256_GCM_SHA384
RSA
RSA
AESGCM(256)
AEAD



AES256-SHA256
(Weak)
TLSv1.2
0x00,0x3D
No FS

TLS_RSA_WITH_AES_256_CBC_SHA256
RSA
RSA
AES(256)
SHA256



ECDHE-RSA-AES128-SHA256
(Weak)
TLSv1.2
0xC0,0x27
FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
ECDH
RSA
AES(128)
SHA256



AES128-GCM-SHA256
(Weak)
TLSv1.2
0x00,0x9C
No FS

TLS_RSA_WITH_AES_128_GCM_SHA256
RSA
RSA
AESGCM(128)
AEAD



AES128-SHA256
(Weak)
TLSv1.2
0x00,0x3C
No FS

TLS_RSA_WITH_AES_128_CBC_SHA256
RSA
RSA
AES(128)
SHA256



ECDHE-RSA-AES256-SHA
(Weak)
TLSv1
0xC0,0x14
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
ECDH
RSA
AES(256)
SHA1



ECDHE-RSA-AES128-SHA
(Weak)
TLSv1
0xC0,0x13
FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
ECDH
RSA
AES(128)
SHA1



CAMELLIA256-SHA
(Weak)
SSLv3
0x00,0x84
No FS

TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
RSA
RSA
Camellia(256)
SHA1



AES256-SHA
(Weak)
SSLv3
0x00,0x35
No FS

TLS_RSA_WITH_AES_256_CBC_SHA
RSA
RSA
AES(256)
SHA1



CAMELLIA128-SHA
(Weak)
SSLv3
0x00,0x41
No FS

TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
RSA
RSA
Camellia(128)
SHA1



AES128-SHA
(Weak)
SSLv3
0x00,0x2F
No FS

TLS_RSA_WITH_AES_128_CBC_SHA
RSA
RSA
AES(128)
SHA1
www.ooredoo.tn
196.203.59.19
443
ECDHE-RSA-CHACHA20-POLY1305
(Secure)
TLSv1.2
0xCC,0xA8
FS
15 Ciphers, 82.18 sec
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
ECDH
RSA
CHACHA20/POLY1305(256)
AEAD



ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
ECDH
RSA
AESGCM(256)
AEAD



ECDHE-RSA-AES128-GCM-SHA256
(Secure)
TLSv1.2
0xC0,0x2F
FS

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
ECDH
RSA
AESGCM(128)
AEAD



ECDHE-RSA-AES256-SHA384
(Weak)
TLSv1.2
0xC0,0x28
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
ECDH
RSA
AES(256)
SHA384



AES256-GCM-SHA384
(Weak)
TLSv1.2
0x00,0x9D
No FS

TLS_RSA_WITH_AES_256_GCM_SHA384
RSA
RSA
AESGCM(256)
AEAD



AES256-SHA256
(Weak)
TLSv1.2
0x00,0x3D
No FS

TLS_RSA_WITH_AES_256_CBC_SHA256
RSA
RSA
AES(256)
SHA256



ECDHE-RSA-AES128-SHA256
(Weak)
TLSv1.2
0xC0,0x27
FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
ECDH
RSA
AES(128)
SHA256



AES128-GCM-SHA256
(Weak)
TLSv1.2
0x00,0x9C
No FS

TLS_RSA_WITH_AES_128_GCM_SHA256
RSA
RSA
AESGCM(128)
AEAD



AES128-SHA256
(Weak)
TLSv1.2
0x00,0x3C
No FS

TLS_RSA_WITH_AES_128_CBC_SHA256
RSA
RSA
AES(128)
SHA256



ECDHE-RSA-AES256-SHA
(Weak)
TLSv1
0xC0,0x14
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
ECDH
RSA
AES(256)
SHA1



ECDHE-RSA-AES128-SHA
(Weak)
TLSv1
0xC0,0x13
FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
ECDH
RSA
AES(128)
SHA1



CAMELLIA256-SHA
(Weak)
SSLv3
0x00,0x84
No FS

TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
RSA
RSA
Camellia(256)
SHA1



AES256-SHA
(Weak)
SSLv3
0x00,0x35
No FS

TLS_RSA_WITH_AES_256_CBC_SHA
RSA
RSA
AES(256)
SHA1



CAMELLIA128-SHA
(Weak)
SSLv3
0x00,0x41
No FS

TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
RSA
RSA
Camellia(128)
SHA1



AES128-SHA
(Weak)
SSLv3
0x00,0x2F
No FS

TLS_RSA_WITH_AES_128_CBC_SHA
RSA
RSA
AES(128)
SHA1


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=88edda95-edad-4f52-8a83-852ac8b38dee


Last Result: https://check-your-website.server-daten.de/?q=ooredoo.tn - 2024-07-10 12:29:38


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.tn" target="_blank">Check this Site: ooredoo.tn</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