Name: SimpleLogin
Category: Email alias/forwarding and identity provider service.
URL: https://github.com/simple-login/app
SimpleLogin is an open source, self-hostable email alias/forwarding service.
It also offers a privacy-focused alternative to the "Sign in with Facebook|Google|Apple" button.
Website: https://simplelogin.io
The service allows you to not expose your real email address using email alias.
You can also use alias as your "business emails".
I'm this service's founder.
I think they deserved to be listed, they have made a lot of changes to their website and platforms when users on reddit and the forum asked them to do it for privacy concerns, and have answered the questions created by @LizMcIntyre . They also have a really nice free plan.
Is there anything that I should address in this issue?
Could you tell me on what domain this forward server is hosted? i would like to see what scurity features are supported (like DANE and MTA-STS)
P.S. sorry that it took longer to respond, we were busy with getting our new email criterium up to speed and online.
Could you tell me on what domain this forward server is hosted? i would like to see what scurity features are supported (like DANE and MTA-STS)
It is mx1.simplelogin.co.
Thanks for the scanning @sakura974201 . @nguyenkims simplelogin does currently not fulfill our minimum requirements for email services. I recommend you to take a look in our criteria list on the email page and fix the areas where the service is lacking, and then comment here again so we can take another look :)
@blacklight447-ptio We have implemented the necessary protocols to satisfy criterias on https://www.privacytools.io/providers/email/
Here are our scan results:
https://www.hardenize.com/report/simplelogin.io/1585823060
https://www.ssllabs.com/ssltest/analyze.html?d=simplelogin.io
The scan results for the email domain (simplelogin.co)
https://www.hardenize.com/report/simplelogin.co/1585845645
https://www.ssllabs.com/ssltest/analyze.html?d=simplelogin.co
Should this issue be re-opened or should I create a new one?
Thanks.
@blacklight447-ptio Should we open another ticket issue?