SSL-Tools

SSL check results of nevtelen.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for nevtelen.com 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 Sat, 27 Apr 2024 16:38:19 +0000

The mailservers of nevtelen.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @nevtelen.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
omg.itsfailing.com
2a01:4f8:1c17:65a7::1
 10
supported
nevtelen.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
omg.itsfailing.com
138.201.156.10
 10
supported
nevtelen.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=nevtelen.com

Certificate chain
  • nevtelen.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • nevtelen.com
Alternative Names
  • mail.nevtelen.com
  • nevtelen.com
  • omg.itsfailing.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-25
Not valid after
2024-06-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
57:62:AA:1D:62:18:72:4F:5A:C9:B6:14:EF:C6:E7:1E:12:A7:10:E1:05:26:21:96:48:FA:8D:52:9C:F8:65:DD
SHA1
DD:9F:7F:E7:C7:71:1C:62:16:BB:BB:66:C2:EA:7C:E5:6D:C2:EE:A1
X509v3 extensions
subjectKeyIdentifier
  • AA:64:F6:4A:21:53:C0:84:9F:5B:F6:ED:8B:7B:0F:5C:F0:A6:C7:A1
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.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 : Mar 26 00:58:40.105 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FC:31:89:CE:AB:4F:6F:48:22:A3:01:
  • 72:A6:A8:65:BA:07:65:18:FB:64:69:FE:61:C4:62:E3:
  • FF:90:32:7E:93:02:20:22:9F:C5:8D:17:66:6C:15:08:
  • 47:36:22:AA:9A:F1:11:C9:16:3D:D8:83:2B:D6:2E:29:
  • 6F:11:38:DF:FB:6A:EF
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 26 00:58:40.112 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A2:50:55:A8:DC:6C:23:83:70:9D:79:
  • B9:43:4A:FE:99:2D:D5:45:9E:D6:2E:56:0A:50:77:7F:
  • A5:FF:53:40:E6:02:20:3A:45:AF:15:75:67:3F:14:29:
  • 21:9E:9F:47:C8:90:60:51:65:65:3C:34:AF:2C:E1:34:
  • C9:E6:03:6C:04:98:A7