SSL check results of dev-urandom.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for dev-urandom.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 Fri, 20 Nov 2020 14:07:04 +0000

We can not guarantee a secure connection to the mailservers of dev-urandom.net!

Please contact the operator of dev-urandom.net and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/dev-urandom.net

Servers

Incoming Mails

These servers are responsible for incoming mails to @dev-urandom.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.dev-urandom.net
2a01:4f8:c17:6953::10
Results incomplete
10
unsupported
not checked
DANE
errors
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx.dev-urandom.net
88.99.39.123
10
supported
dev-urandom.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

We have received emails from these servers with @dev-urandom.net sender addresses. Test mail delivery

Host TLS Version & Cipher
mx.dev-urandom.net (88.99.39.123)
TLSv1.3 TLS_AES_256_GCM_SHA384
mx.dev-urandom.net (IPv6:2a01:4f8:c17:6953::10)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=dev-urandom.net

Certificate chain
Subject
Common Name (CN)
  • dev-urandom.net
Alternative Names
  • *.dev-urandom.net
  • dev-urandom.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-10-01
Not valid after
2020-12-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
11:E6:3E:AA:63:98:A9:8B:EA:A1:21:35:FA:65:08:4E:E6:BA:9E:2F:9C:60:B3:06:0E:32:CA:BC:98:5E:B8:6A
SHA1
18:AE:BD:80:2F:D2:5C:1E:51:28:7B:0A:C4:85:D3:D9:C5:98:8A:41
X509v3 extensions
subjectKeyIdentifier
  • E8:68:A8:A4:90:FF:F6:C8:E8:6D:EE:9D:5D:1D:40:71:F7:4D:8F:69
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F0:95:A4:59:F2:00:D1:82:40:10:2D:2F:93:88:8E:AD:
  • 4B:FE:1D:47:E3:99:E1:D0:34:A6:B0:A8:AA:8E:B2:73
  • Timestamp : Oct 1 02:33:42.503 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F0:50:80:F7:DA:09:81:1C:1A:9D:4B:
  • 64:B7:9E:C2:23:A0:93:16:81:A8:65:83:97:10:2B:4F:
  • E1:56:DD:B0:F1:02:20:04:0F:92:F9:13:6D:28:5E:0A:
  • B2:65:08:C8:62:07:4B:1D:D4:D2:42:C5:4F:69:70:0A:
  • 96:A2:52:0D:91:1A:EF
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : Oct 1 02:33:42.983 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0B:74:38:74:A9:88:93:11:CC:88:65:56:
  • 75:C0:F1:63:7E:BC:15:96:3A:30:4D:0E:BB:26:86:F7:
  • 27:F8:90:1D:02:21:00:A8:2A:56:27:2F:49:A0:74:E0:
  • DF:33:08:58:0E:0E:0B:D3:E9:4F:0B:E9:6B:79:E1:CE:
  • 67:DA:18:92:4F:69:39

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mx.dev-urandom.net
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
valid