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

0 in Queue, 0 of max. 8 Checks (13:31:01)
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 |

 

T

 

Timeout

 

Checked:
31.08.2026 22:20:55

 

Older results

 

T - 28.11.2025 01:33:26
T - 01.11.2025 22:28:16
T - 29.10.2025 06:13:06
T - 27.09.2025 00:52:46
T - 06.04.2025 15:06:38
T - 25.03.2025 06:38:45
T - 20.02.2025 09:39:27
T - 16.02.2025 20:11:38
T - 10.01.2025 19:46:34
T - 16.12.2024 06:41:16

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
ooredoo.tn
A
154.72.227.22
Tunis/Tunis Governorate/Tunisia (TN) - ooredoo TN
No Hostname found
yes
1
0

AAAA

yes


www.ooredoo.tn
A
154.72.227.22
Tunis/Tunis Governorate/Tunisia (TN) - ooredoo TN
No Hostname found
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 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 57780, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 20.09.2026, 00:00:00 +, Signature-Inception: 30.08.2026, 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: 13.09.2026, 17:00:00 +, Signature-Inception: 31.08.2026, 16:00:00 +, KeyTag 57780, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 57780 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: 12.09.2026, 13:42:01 +, Signature-Inception: 28.08.2026, 13:00:02 +, KeyTag 8629, Signer-Name: tn






RRSIG-Owner tn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.09.2026, 13:42:01 +, Signature-Inception: 28.08.2026, 13:00:02 +, 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: 12.09.2026, 16:30:50 +, Signature-Inception: 28.08.2026, 15:32:13 +, 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: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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: 154.72.227.22
Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn






RRSIG Type 16 validates the TXT - Result: v=spf1 include:_netblocks.ooredoo.tn include:_netblocks2.ooredoo.tn -all
Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 60 sec, Signature-expiration: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 00:00:00 +, KeyTag 7481, Signer-Name: ooredoo.tn






Status: Good. NoData-Proof required and found.






AAAA-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 AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ooredoo.tn., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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: 154.72.227.22
Validated: RRSIG-Owner www.ooredoo.tn., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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: 3600 sec, Signature-expiration: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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: 10.09.2026, 00:00:00 +, Signature-Inception: 20.08.2026, 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
Tunis/Tunis 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 / BNS53
•

•  ns2.ati.tn / KNS53
•

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

•  ns-tn.afrinic.net / S01-260122-NS2-PKL
•

•  pch.ati.tn / 8.fra.pch
•

•  rip.psg.com / rip.psg.com
•

 

4. SOA-Entries


Domain:tn
Zone-Name:tn
Primary:ns1.ati.tn
Mail:hostmaster.ati.tn
Serial:2026159261
Refresh:21600
Retry:10800
Expire:604800
TTL:60
num Entries:1


Domain:tn
Zone-Name:tn
Primary:ns1.ati.tn
Mail:hostmaster.ati.tn
Serial:2026159262
Refresh:21600
Retry:10800
Expire:604800
TTL:60
num Entries:5


Domain:ooredoo.tn
Zone-Name:ooredoo.tn
Primary:ns1.ooredoo.tn
Mail:admin.ooredoo.tn
Serial:2026083102
Refresh:14400
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:2026083102
Refresh:14400
Retry:3600
Expire:604800
TTL:3600
num Entries:1


5. Screenshots

Startaddress: https://www.ooredoo.tn/, address used: https://www.ooredoo.tn/Personal/fr/, Screenshot created 2024-12-16 06:49:58 +00:0 url is insecure, certificate invalid

 

Mobil (412px x 732px)

 

4959 milliseconds

 

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

 

5462 milliseconds

 

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

 

3985 milliseconds

 

Screenshot Desktop - https://www.ooredoo.tn/Personal/fr/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size4125744

 

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

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://ooredoo.tn/
154.72.227.22
302
https://ooredoo.tn/

0.127
A
Location: https://ooredoo.tn/
Connection: Keep-Alive
Content-Length: 0

• http://www.ooredoo.tn/
154.72.227.22
302
https://www.ooredoo.tn/

0.063
A
Location: https://www.ooredoo.tn/
Connection: Keep-Alive
Content-Length: 0

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


10.043
T
Timeout - The operation has timed out.

• https://ooredoo.tn/
154.72.227.22
301
http://www.ooredoo.tn/
Html is minified: 103.14 %
3.890
F
Date: Mon, 31 Aug 2026 20:21:59 GMT
Location: http://www.ooredoo.tn/
Set-Cookie: TS019bcb7f=01e05c51db5097fdf18bab1dfb1fa315d3388fe5269895dd36b432ae6b874c047f93c2f0027ef465bc28d2fe3a09cff374ed3117cf; Path=/; Domain=.ooredoo.tn; 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/
154.72.227.22
302
https://www.ooredoo.tn/Personal/

3.923
B
Date: Mon, 31 Aug 2026 20:22:04 GMT
X-Frame-Options: SAMEORIGIN
Vary: Host
Location: https://www.ooredoo.tn/Personal/
Set-Cookie: TS0138d5e7=01e05c51dbe676a30cf8afd1208501da2291c15aa66820f7d230e02eaff8730b00068fac39afa37191928d2680051fcbd90b04cbea; Path=/; Domain=.www.ooredoo.tn; Secure; Httponly
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=16070400; includeSubDomains
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Content-Length: 0

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


10.030
T
Timeout - The operation has timed out.

• https://www.ooredoo.tn/Personal/

-14


10.043
T
Timeout - The operation has timed out.

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

0.063
A
Visible Content:
Location: https://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Connection: Keep-Alive
Content-Length: 0

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

0.063
A
Visible Content:
Location: https://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Connection: Keep-Alive
Content-Length: 0

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


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

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

Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
http://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 102.40 %
Other inline scripts (∑/total): 0/0		3.593
B
Visible Content:
Date: Mon, 31 Aug 2026 20:22:54 GMT
Location: http://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Set-Cookie: TS019bcb7f=01e05c51db4673b94c39522f9456276be0f257f54ad522d3517895e32bfe1643f0af6aefc80f0cfb50eb0aba160fa3b847a1a99c2c; Path=/; Domain=.ooredoo.tn; 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: 299
Content-Type: text/html; charset=iso-8859-1

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

-14


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

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

Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0		3.827
N
Certificate error: RemoteCertificateNameMismatch
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Cache-Control: no-cache
Connection: close
Pragma: no-cache
Strict-Transport-Security: max-age=16070400; includeSubDomains
Content-Type: text/html; charset=utf-8
Content-Length: 110

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


10.047
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: 39 (complete: 276475)
AGood: All ip addresses are public addresses
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: www.ooredoo.tn has 1 ipv4, 1 ipv6 addresses
Warning: Only one ip address found: ooredoo.tn 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.tn has no ipv6 address.
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/ 154.72.227.22
302
https://ooredoo.tn/
Correct redirect http - https with the same domain name
Ahttp://www.ooredoo.tn/ 154.72.227.22
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/ 154.72.227.22
301
TS019bcb7f=01e05c51db5097fdf18bab1dfb1fa315d3388fe5269895dd36b432ae6b874c047f93c2f0027ef465bc28d2fe3a09cff374ed3117cf; 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://www.ooredoo.tn/ 154.72.227.22
302
TS0138d5e7=01e05c51dbe676a30cf8afd1208501da2291c15aa66820f7d230e02eaff8730b00068fac39afa37191928d2680051fcbd90b04cbea; 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://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
301
TS019bcb7f=01e05c51db4673b94c39522f9456276be0f257f54ad522d3517895e32bfe1643f0af6aefc80f0cfb50eb0aba160fa3b847a1a99c2c; 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.
Fhttps://ooredoo.tn/ 154.72.227.22
301
http://www.ooredoo.tn/
Wrong redirect https - http - never redirect https to http
Fhttps://ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
301
http://www.ooredoo.tn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect https - http - never redirect https to http
Khttp://www.ooredoo.tn/ 154.72.227.22, Status 302

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

https://www.ooredoo.tn/ 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 154.72.227.22, 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://154.72.227.22/ 154.72.227.22
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Oooredoo.tn / 154.72.227.22 / 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. 12 Cipher Suites without Forward Secrecy found
Owww.ooredoo.tn / 154.72.227.22 / 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. 12 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 www.ooredoo.tn, 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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain ooredoo.tn, 1 ip addresses, 1 different http results.
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

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
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://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://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://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 154.72.227.22, 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://154.72.227.22/ 154.72.227.22
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.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
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: 347370 milliseconds, 347.370 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
ooredoo.tn
154.72.227.22
443
ok
Tls12
ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok
ooredoo.tn
154.72.227.22
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 Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB


3CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB


4CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, C=US, ST=New Jersey


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

www.ooredoo.tn
154.72.227.22
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 Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB


3CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB


4CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, C=US, ST=New Jersey


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

ooredoo.tn
ooredoo.tn
443
ok
Tls12

ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - incomplete

1CN=*.ooredoo.tn


2CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB


3CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB


4CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, C=US, ST=New Jersey


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

154.72.227.22
154.72.227.22
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 Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB


3CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB


4CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, C=US, ST=New Jersey

 

9. Certificates

1.
1.
CN=*.ooredoo.tn
06.01.2026
29.09.2026
expires in 24 days		*.ooredoo.tn, ooredoo.tn - 2 entries
1.
1.
CN=*.ooredoo.tn
06.01.2026

29.09.2026
expires in 24 days


*.ooredoo.tn, ooredoo.tn - 2 entries

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:45B519FE85487681CC6AD309AA9D595A
Thumbprint:A3383971BD189AC94119D01423051F880E0C7FBD
SHA256 / Certificate:9KP63ChcGNpGwNxLKylLgAStPfjbATnTe7FgjND/oac=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):76f2c203be86702d369bac0e6ea4852decea6fa6b350d5e6c7a0928c6deb9ff4
SHA256 hex / Subject Public Key Information (SPKI):76f2c203be86702d369bac0e6ea4852decea6fa6b350d5e6c7a0928c6deb9ff4 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
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=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
22.03.2021
22.03.2036
expires in 3486 days

2.
CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
22.03.2021

22.03.2036
expires in 3486 days




KeyalgorithmRSA encryption ( bit)
Signatur:SHA384 With RSA Encryption
Serial Number:397A66CC2756362E0DAA87CA6EABE3B1
Thumbprint:DD55B4520291E276588F0DD02FAFD83A7368E0FA
SHA256 / Certificate:jFTDNLZrpOQmdyr0o/kTbBmhrscp/bKMU1wHpaTvIuA=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):6bd9212ce649c659c9cabc6cb60fcffac7a20c29be61fdceb2b5f2168701688d
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.sectigo.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)




3.
CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB
22.03.2021
22.03.2046
expires in 7138 days

3.
CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB
22.03.2021

22.03.2046
expires in 7138 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA384 With RSA Encryption
Serial Number:758DFD8BAE7C0700FAA925A7E1C7AD14
Thumbprint:AD98F9F3E47D753B65D482B3A45217BB6EF5E438
SHA256 / Certificate:e7ZHpirurIi/JXqlItAf/qOV4KtFxz+T9lZU7DjyWgY=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):0e8bb18bbeefb381be21bfc1a206d317298462ad104855f04a0542699708d3d4
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
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
0
3
CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
0
2
2
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
13338381895
leaf cert		CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
2026-01-06 00:00:00
2026-09-28 23:59:59
*.ooredoo.tn, ooredoo.tn - 2 entries


13326557660
leaf cert		CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
2026-01-05 00:00:00
2026-09-28 23:59:59
*.ooredoo.tn, ooredoo.tn - 2 entries


8845562026
leaf cert		CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2024-12-05 00:00:00
2026-01-05 23:59:59
*.ooredoo.tn, ooredoo.tn - 2 entries


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
0
3

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


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. 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: ns1.ooredoo.tn, ns2.ooredoo.tn, ns3.ooredoo.tn

 

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

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

 

14. 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

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
ooredoo.tn
v=spf1 include:_netblocks.ooredoo.tn include:_netblocks2.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

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

ooredoo.tn
5
corpas2.ooredoo.tn
02ok

A


154.72.227.113
01ok

CNAME


00ok
MX

ooredoo.tn
5
corpas1.ooredoo.tn
02ok

A


154.72.227.112
01ok

CNAME


00ok
SPF
TXT
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.

				 
			

				 
			
17. Cipher Suites
Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
ooredoo.tn
154.72.227.22
443
19 Ciphers89.11 sec
12 without, 7 FS
36.84 %
www.ooredoo.tn
154.72.227.22
443
19 Ciphers87.99 sec
12 without, 7 FS
36.84 %
Complete

2
38 Ciphers
19.00 Ciphers/Check		177.10 sec88.55 sec/Check
24 without, 14 FS
36.84 %

Details
DomainIPPortCipher (OpenSsl / IANA)
ooredoo.tn
154.72.227.22
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
19 Ciphers, 

89.11 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




AES256-CCM8
 (Weak)
TLSv1.2
0xC0,0xA1
 No FS

TLS_RSA_WITH_AES_256_CCM_8

RSA
RSA
AESCCM8(256)
AEAD




AES256-CCM
 (Weak)
TLSv1.2
0xC0,0x9D
 No FS

TLS_RSA_WITH_AES_256_CCM

RSA
RSA
AESCCM(256)
AEAD




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




AES128-CCM8
 (Weak)
TLSv1.2
0xC0,0xA0
 No FS

TLS_RSA_WITH_AES_128_CCM_8

RSA
RSA
AESCCM8(128)
AEAD




AES128-CCM
 (Weak)
TLSv1.2
0xC0,0x9C
 No FS

TLS_RSA_WITH_AES_128_CCM

RSA
RSA
AESCCM(128)
AEAD




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
154.72.227.22
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
19 Ciphers, 

87.99 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




AES256-CCM8
 (Weak)
TLSv1.2
0xC0,0xA1
 No FS

TLS_RSA_WITH_AES_256_CCM_8

RSA
RSA
AESCCM8(256)
AEAD




AES256-CCM
 (Weak)
TLSv1.2
0xC0,0x9D
 No FS

TLS_RSA_WITH_AES_256_CCM

RSA
RSA
AESCCM(256)
AEAD




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




AES128-CCM8
 (Weak)
TLSv1.2
0xC0,0xA0
 No FS

TLS_RSA_WITH_AES_128_CCM_8

RSA
RSA
AESCCM8(128)
AEAD




AES128-CCM
 (Weak)
TLSv1.2
0xC0,0x9C
 No FS

TLS_RSA_WITH_AES_128_CCM

RSA
RSA
AESCCM(128)
AEAD




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


				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=3bca45a4-052b-4306-9ccb-8678223cd087

				 
			


Last Result: https://check-your-website.server-daten.de/?q=ooredoo.tn - 2026-08-31 22:20:55

				 
			
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 - https://check-your-website.server-daten.de/?d=ooredoo.tn

				 
			

				 
			



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