SSL-Tools

SSL check results of budgie.id.au

NEW You can also bulk check multiple servers.

Discover if the mail servers for budgie.id.au 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 11:36:47 +0000

The mailservers of budgie.id.au can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @budgie.id.au addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.budgie.id.au
2402:9e80:24::1:1:4:19
 0
supported
mx.budgie.id.au
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
20 s
mx.budgie.id.au
119.18.12.162
 0
supported
mx.budgie.id.au
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
15 s
mxdr.budgie.id.au
54.153.210.57
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

We have not received any emails from a @budgie.id.au address so far. Test mail delivery

Certificates

First seen at:

CN=mx.budgie.id.au

Certificate chain
  • mx.budgie.id.au
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx.budgie.id.au
Alternative Names
  • mx.budgie.id.au
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-31
Not valid after
2024-06-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FA:AB:6D:B8:B5:FD:27:32:08:46:47:98:D0:33:8B:00:94:03:89:83:21:7F:B7:65:14:5D:CE:80:93:C0:D4:3A
SHA1
A8:BD:BD:AC:97:D9:8A:4E:2A:E3:AB:A2:98:F3:8C:32:12:22:05:26
X509v3 extensions
subjectKeyIdentifier
  • 18:C2:37:2A:52:77:AD:C0:42:9C:92:03:42:51:DA:2F:FB:97:A2:84
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 31 14:52:27.506 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5A:9A:77:7D:0C:FF:16:CD:9A:DC:66:85:
  • 6E:64:F1:CF:D8:33:24:1C:47:B8:27:FD:FE:2C:EE:F2:
  • C2:AB:E5:99:02:21:00:B2:51:F5:46:0D:6C:BA:68:89:
  • 96:C6:FD:1F:21:BB:0A:1B:68:33:72:FA:13:20:E6:1C:
  • 46:6F:AE:7F:D6:63:C3
  • 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 31 14:52:27.523 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E0:7A:16:F7:C6:CB:96:16:E2:5A:EA:
  • A3:B9:D6:E3:70:39:C7:4B:C7:1D:5F:D5:76:A1:2C:B5:
  • 6B:8E:4E:4C:D8:02:20:1E:32:2A:68:AD:94:30:E0:A0:
  • DB:DE:20:C8:1E:06:97:03:EE:E9:95:B4:96:19:5E:9F:
  • 58:06:E1:F9:8F:F8:BB