SSL check results of jdfpg.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for jdfpg.net 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

Report created Mon, 18 Nov 2024 04:42:07 +0000

The mailservers of jdfpg.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @jdfpg.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.jdfpg.net
121.200.234.204
10
supported
mail.jdfpg.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
24 s
liam.jdfpg.net
203.19.141.164
20
supported
liam.jdfpg.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
27 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.jdfpg.net

Certificate chain
  • mail.jdfpg.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mail.jdfpg.net
Alternative Names
  • mail.jdfpg.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2024-11-18
Not valid after
2025-02-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
93:80:3A:0F:88:2D:58:80:46:6A:1F:7B:DD:5E:E7:8E:55:55:11:89:D1:FB:0C:07:BE:30:BA:44:81:55:FE:CE
SHA1
C8:85:B5:BF:75:40:57:92:B0:9D:8A:76:E1:E0:A0:B2:EA:07:42:2F
X509v3 extensions
subjectKeyIdentifier
  • 4B:0D:B1:3A:33:D7:EA:20:F2:8D:75:FF:45:F5:79:55:09:2C:97:74
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Nov 18 04:41:36.776 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:00:95:7C:D7:BB:74:43:20:47:C8:BF:90:
  • 83:8C:3E:1D:6E:24:55:59:3D:7F:CD:18:02:35:BD:15:
  • 06:42:E3:5C:02:20:6E:45:AC:4E:27:16:C5:C7:46:8E:
  • D0:05:87:72:04:49:17:01:3B:B4:54:08:DA:BA:94:B4:
  • 74:43:91:24:4E:3F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Nov 18 04:41:36.813 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:06:2B:92:66:44:35:82:F3:CB:CC:1F:16:
  • 81:43:84:62:7F:AC:4D:FE:5D:4E:5B:67:B2:3F:79:CD:
  • 97:80:DD:5F:02:21:00:84:BB:5B:32:CC:A3:12:B7:8B:
  • E0:48:C1:8B:9C:E0:91:3F:6E:B6:65:40:F6:F6:47:9C:
  • 2A:EE:E9:31:E7:5A:D2
First seen at:

CN=liam.jdfpg.net

Certificate chain
  • liam.jdfpg.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • liam.jdfpg.net
Alternative Names
  • liam.jdfpg.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2024-11-11
Not valid after
2025-02-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E4:6C:56:6A:3D:4B:ED:90:78:70:EF:59:F4:AC:A2:57:09:11:64:51:D4:72:CC:A9:72:74:DB:C0:2A:A8:EF:D0
SHA1
39:18:77:CA:4B:13:6B:59:7C:CE:94:15:B0:25:F3:C2:2D:8F:3D:22
X509v3 extensions
subjectKeyIdentifier
  • C3:FF:DB:C1:5F:E9:B4:6A:01:80:90:32:AA:86:2C:F5:5B:4C:B4:AF
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Nov 11 14:55:50.231 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:23:55:C8:38:62:E8:F3:B3:20:B7:70:C7:
  • 2C:A4:8F:7F:61:8E:CC:AF:BD:E8:99:62:2B:89:36:34:
  • A8:27:68:12:02:20:43:BF:8A:D3:ED:68:33:D6:DF:78:
  • 9D:99:B1:EE:EF:71:FC:CF:F7:CF:3D:C5:27:1B:CC:0D:
  • 62:AC:57:B2:E5:C4
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Nov 11 14:55:50.255 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6F:B8:95:7D:AE:24:7C:86:E1:06:9B:50:
  • 20:CC:B5:D2:B5:0C:9F:5D:80:7A:8A:B4:2A:22:D0:93:
  • 90:BE:F6:7F:02:21:00:98:50:46:EC:EA:72:F5:5B:F8:
  • A7:62:3F:37:78:C2:F2:35:55:9D:8E:F3:E2:CE:38:E0:
  • 91:BD:EB:03:BA:A0:0E