SSL-Tools

SSL check results of oidq.dev

NEW You can also bulk check multiple servers.

Discover if the mail servers for oidq.dev 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 Fri, 19 Apr 2024 09:02:31 +0000

The mailservers of oidq.dev can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @oidq.dev addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
arthur.oidq.dev
2001:bc8:1640:107e:dc00:ff:fe1c:1593
 10
supported
arthur.oidq.dev
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
arthur.oidq.dev
51.158.183.212
 10
supported
arthur.oidq.dev
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=arthur.oidq.dev

Certificate chain
  • arthur.oidq.dev
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • arthur.oidq.dev
Alternative Names
  • arthur.oidq.dev
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-11
Not valid after
2024-06-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
32:26:5A:D2:B6:1E:8E:78:C5:5C:3C:60:11:CA:FF:B7:67:26:C6:0B:36:9E:13:63:FC:E5:FD:5B:6D:40:9C:04
SHA1
C8:B4:FD:3A:26:80:02:59:8E:A4:9E:25:E9:7C:2F:3B:86:D3:C6:7C
X509v3 extensions
subjectKeyIdentifier
  • 7E:17:5D:44:75:9D:51:AE:7D:D5:3D:CF:AA:FE:B4:F5:E3:24:3E:A8
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 : 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 11 20:52:20.374 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0F:AD:CE:E3:6F:F6:EA:3C:75:20:9A:D6:
  • 79:D2:77:1C:FA:18:DA:15:A1:7D:77:59:20:A6:70:B5:
  • 58:85:80:22:02:21:00:ED:42:74:77:45:C5:39:73:3C:
  • A4:F7:5F:45:FB:B7:99:0A:50:7C:F4:CC:55:AC:E2:7F:
  • 03:CB:0F:F4:38:D3:48
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 11 20:52:20.384 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8B:BB:F2:18:08:0D:2B:E7:DD:6F:BB:
  • E0:96:37:DE:2C:84:C5:86:11:47:56:A8:F7:17:4E:F3:
  • C7:12:94:EC:E8:02:21:00:D4:3D:3E:C8:E4:60:76:3C:
  • 7C:4D:14:8E:C2:5A:45:39:99:7B:89:FE:38:58:37:44:
  • BB:B2:48:D3:3B:0C:44:C9

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.arthur.oidq.dev
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid