SSL check results of bungie.com

NEW You can also bulk check multiple servers.

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

Report created Sun, 23 Aug 2020 23:09:08 +0000

The mailservers of bungie.com can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp3.bungie.com
66.62.245.96
10
supported
smtp.bungie.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
19 s
smtp4.bungie.com
66.62.245.97
10
supported
smtp.bungie.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
18 s

Outgoing Mails

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

Certificates

First seen at:

OU=IT,ST=WA,O=Bungie,L=Bellevue,CN=smtp.bungie.com,C=US

Certificate chain
  • smtp.bungie.com (Certificate is self-signed.)
    • remaining
    • 2048 bit
    • sha1WithRSAEncryption
    • Hostname Mismatch
    • Unknown Authority

Subject
Country (C)
  • US
Common Name (CN)
  • smtp.bungie.com
Locality (L)
  • Bellevue
Organization (O)
  • Bungie
State (ST)
  • WA
Organizational Unit (OU)
  • IT
Issuer

Certificate is self-signed.

validity period
Not valid before
2016-03-18
Not valid after
2026-03-16
Fingerprints
SHA256
8E:8A:3D:DC:E1:1A:B6:72:25:38:19:65:99:2D:70:8B:96:42:FE:4B:8B:14:AE:C9:0F:16:8B:CB:A2:8D:60:EB
SHA1
0C:E9:E6:BD:3F:C7:41:76:FE:FB:D9:F4:3A:9D:0B:4C:EA:44:E9:F6