SSL-Tools

SSL check results of mamabaji.ai.in

NEW You can also bulk check multiple servers.

Discover if the mail servers for mamabaji.ai.in 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 Sun, 13 Apr 2025 18:08:07 +0000

We can not guarantee a secure connection to the mailservers of mamabaji.ai.in!

Please contact the operator of mamabaji.ai.in and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/mamabaji.ai.in

Servers

Incoming Mails

These servers are responsible for incoming mails to @mamabaji.ai.in addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
one.mxroute.com
49.12.120.198
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
one-relay.mxroute.com
49.12.120.198
 20
supported
sunfire.mxrouting.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @mamabaji.ai.in address so far. Test mail delivery

Certificates

First seen at:

CN=sunfire.mxrouting.net

Certificate chain
  • sunfire.mxrouting.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
    • Hostname Mismatch
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • sunfire.mxrouting.net
Alternative Names
  • sunfire.mxrouting.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2025-03-07
Not valid after
2025-06-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
94:1D:2D:1B:3D:26:0B:BF:09:58:FA:23:FC:FF:62:94:B6:A5:76:D4:83:1D:1F:B2:B3:5D:5C:55:D3:9A:AD:DE
SHA1
17:CC:AF:3E:45:C5:10:F2:1F:A1:5C:73:4B:45:5F:D1:77:48:5C:4C
X509v3 extensions
subjectKeyIdentifier
  • E7:AE:9D:74:84:D4:B9:57:66:3E:34:E4:A6:86:13:1C:64:A4:4B:74
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Mar 7 02:14:37.138 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E7:A5:C9:9E:14:5C:7F:E6:39:88:58:
  • D3:88:A8:9A:FB:4A:5B:CC:62:2D:2D:4C:B8:9C:BF:19:
  • 28:15:87:13:68:02:20:6D:B7:56:E1:6F:F0:B2:D0:43:
  • 1F:F3:B9:E7:4B:81:C8:78:C2:98:2C:AB:56:6B:D6:9A:
  • F7:09:A2:39:DE:9D:19
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Mar 7 02:14:37.151 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:94:E8:14:25:2A:3F:5A:CE:AE:F4:87:
  • 4B:FC:02:A4:90:14:7D:0B:8B:58:F6:1F:F9:10:27:43:
  • D6:C2:BC:AA:FA:02:21:00:97:89:AB:FD:56:19:FF:F8:
  • 32:87:01:9E:32:66:26:B5:FA:45:F8:A7:4A:FD:92:D6:
  • A4:6D:20:74:B6:3D:13:BE