eMail Challenges and How We Solve Them
You receive confidential information by email and you want to know how secure your email address is. Use our /email/test To: on your own email address.
You send confidential information by email and want to know how secure the other person's email is. Test their address with the same /email/test To: test.
If /email/testTo: shows that something is wrong, use the Detail output level of that test to expose the problem.
Since you are responsible for security when sending confidential information, you want to know how securely you send email. Send us an email using /email/test From: and we'll let you know.
But what about your home email account, can it send secure email? Remember it uses special settings from your Internet Provider to receive email from your PC. Use our Full Version Receiver Test. It lets you enter settings like SMTP host, port, and your user-id and password.
At work, company policy requires that you have to use TLS with certain trading partners. Your email server has a "require" or "mandatory" TLS setting, but is it working? Don't you need a broken email system to test it with? Use our /email/test mandatory From: to make sure your end is working, and /email/test mandatory To: to make sure the other guy's end is working.
Your company exchanges sensitive email with a lot of trading partners, and you're asked to check them all. And once you've typed all those email address, it would be nice to give them to someone to keep testing them every now and then. Use our Batch. It's where CheckTLS really starts to show value!
What you'd really like is for someone to just let you know if your email starts to fail over to insecure mode, or if anything happens to one of your trading partners email. Just tell Batch to only send results to you if something's changed. It can even send a pager-friendly text message to your phone.
If only there was a way to be sure that all that silence really meant everything was working, and not that CheckTLS is down or your Batch failed to run? Use our MonitorTLS Web Service. It integrates with most monitoring and notification systems and shows you the date and time that a Batch last ran successfully, providing fail-save monitoring of your Batch and by extension your trading partners.
CheckTLS tests and monitoring can be made to satisfy most contractual and legal requirements (like PHI/HIPAA, PCI, etc.). But let's say your company goes further and inserts an in-line or on-line email security system on the edge of your network. They task you with setting it up, and it's not working. If only you had a network sniffer (and knew how to use it). Use our Internet Sniffer service. You position it inbetween the two sides and it lets you "listen in".
No matter how expensive and redundant that email edge device is, having it monitored independently from outside your network is always a good thing.
If you need an unsigned SSL cert for internal use or to test something, you can make one right here.
Got an encoded cert and you want to know what's in it? Show it right here.
Want to re-key your cert with more bits or a different encryption? You'll need to know exactly what is in the certificate signing request (CSR) you used years ago. Show what's inside a CSR right here.
Your Exchange Server won't sync and you want to telnet to the IMAP port, but you forget the IMAP syntax. And it's all encrypted with TLS anyway, so telnet won't work. Use our IP Services Test. It will test POP, IMAP, HTTP, almost any client/server service, on either the plain-text or the SSL port.
Wherever your needs fall in the above scenarios, CheckTLS is handy to have around, whether it's watching over your email or just as another tool in your kit.