SSL-Tools

SSL check results of mamc.co

NEW You can also bulk check multiple servers.

Discover if the mail servers for mamc.co 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 Wed, 17 Apr 2024 06:02:48 +0000

We can not guarantee a secure connection to the mailservers of mamc.co!

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

/mailservers/mamc.co

Servers

Incoming Mails

These servers are responsible for incoming mails to @mamc.co addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
static-96-242-154-66.nwrknj.fios.verizon.net
96.242.154.66
Results incomplete
5
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.mamc.co
192.250.231.11
 15
supported
p1402.use1.mysecurecloudhost.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s
p1402.use1.mysecurecloudhost.com
192.250.231.11
 15
supported
p1402.use1.mysecurecloudhost.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=p1402.use1.mysecurecloudhost.com

Certificate chain
  • p1402.use1.mysecurecloudhost.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • p1402.use1.mysecurecloudhost.com
Alternative Names
  • p1402.use1.mysecurecloudhost.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-27
Not valid after
2024-05-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
26:AC:BF:5F:48:CE:96:01:77:F5:FE:5E:83:90:AD:C9:B9:9C:F1:DD:8D:51:F4:9D:71:8B:E5:EF:D5:4C:36:C4
SHA1
45:A3:87:8E:37:F7:90:0D:B2:08:BA:3A:48:2B:E6:18:CF:73:38:BB
X509v3 extensions
subjectKeyIdentifier
  • 17:7C:1B:3A:E2:4F:B0:06:49:39:71:F4:71:E2:CB:2C:FC:D6:2B:C0
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 : Feb 27 13:37:35.374 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F5:1F:F1:87:35:7F:19:C1:E4:7F:CB:
  • 6F:61:50:72:EC:84:C7:F0:A6:1A:C2:7E:F1:3B:27:CD:
  • F6:0F:90:A8:F7:02:20:56:23:5A:94:54:2F:EC:A7:2E:
  • 8A:86:35:97:D5:77:7F:4A:AC:5C:DF:C9:C5:B5:E8:1D:
  • B6:B1:1A:5B:63:A9:45
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Feb 27 13:37:35.888 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1E:62:71:A0:CA:3F:50:1B:E8:B6:E3:3B:
  • 6A:3F:BA:EE:66:DB:B6:39:83:F7:3E:3D:40:DF:FC:9D:
  • BA:16:39:31:02:20:12:7F:F8:72:99:23:5D:6D:7D:87:
  • 9E:16:A3:BE:18:1B:03:48:11:12:DF:C2:87:50:47:F8:
  • 92:B9:CB:26:83:DD