SSL-Tools

SSL check results of pamarabasiji.nl

NEW You can also bulk check multiple servers.

Discover if the mail servers for pamarabasiji.nl can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

JSON Refresh

Report created Thu, 05 Sep 2024 08:11:37 +0000

The mailservers of pamarabasiji.nl can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @pamarabasiji.nl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.pamarabasiji.nl
2a02:a469:67fe:1:f64d:30ff:fe6d:132c
 10
supported
mail.pamarabasiji.nl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail.pamarabasiji.nl
77.174.235.101
 10
supported
mail.pamarabasiji.nl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

We have not received any emails from a @pamarabasiji.nl address so far. Test mail delivery

Certificates

First seen at:

CN=mail.pamarabasiji.nl

Certificate chain
  • mail.pamarabasiji.nl
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.pamarabasiji.nl
Alternative Names
  • mail.pamarabasiji.nl
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-07-18
Not valid after
2024-10-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
0B:CE:D4:55:13:D8:E3:D1:FE:E5:D9:4E:67:4B:4D:68:30:43:FA:38:BE:46:9F:00:2C:75:89:BA:A5:E2:64:E3
SHA1
A4:DD:85:81:B6:2A:12:40:B6:BB:69:0F:96:30:03:C2:8B:54:A6:64
X509v3 extensions
subjectKeyIdentifier
  • 55:30:19:31:BF:3D:68:EC:57:7B:94:D9:9B:D0:B1:EC:E2:08:53:70
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Jul 18 12:04:55.206 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:04:74:21:57:86:EE:FC:83:C3:44:08:28:
  • C0:30:BD:E4:68:B2:FE:2C:BD:89:7A:4D:DC:56:3E:EB:
  • F7:43:99:81:02:21:00:D8:E2:82:38:B0:54:1C:54:70:
  • 62:47:5C:B2:84:FF:88:53:87:93:F4:4A:B2:7A:0E:74:
  • 50:D7:ED:D3:52:F6:E5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Jul 18 12:04:55.408 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F5:70:E0:3C:24:B2:84:43:45:52:5E:
  • CC:AC:15:83:F6:3D:1D:8D:1C:27:7B:58:39:60:4D:64:
  • 2F:F5:AC:0B:A5:02:21:00:DF:E3:2E:66:75:44:AB:BD:
  • 91:8C:1F:79:04:DE:7C:49:BD:2E:15:DC:49:B8:4F:36:
  • D5:93:50:F9:F0:EC:FC:0B