Security Overview

Security Overview <p>Keeping your data safe and secure is a huge responsibility and a top priority for us. Here’s how we make it happen.</p> Domains <p>SimpleLogin currently operates on the following domains:</p> <ul> <li></li> <li></li> <li></li> <li></li> </ul> <p>All domains implement the following standards:</p> DNSSEC <p>DNSSEC or Domain Name System Security Extensions is an extension of the DNS protocol that provides cryptographic assurance of the authenticity and integrity of responses. It’s intended as a defense against network attackers who are able to manipulate DNS to redirect their victims to servers of their choice.</p> <p>Without DNSSEC, a malicious hacker can point SimpleLogin MX record to their own server and receive emails sent to SimpleLogin servers.</p> Certification Authority Authorization (CAA) <p>CAA is a standard that allows SimpleLogin to restrict which Certificate Authorities (CA) are allowed to issue certificates for our domains. By default, every public CA is allowed to issue certificates for <strong>any</strong> domain name in the public DNS, provided they validate control of that domain name. That means that if there’s a bug in any one of the many public CAs’ validation processes, every domain name is potentially affected. This has happened in the past, affecting Google, Windows Live among others.</p> <p>CAA provides a way for domain holders to reduce that risk. Without CAA, someone could potentially obtain an unauthorized SSL certificate for SimpleLogin domains that could allow man-in-the-middle hacks.</p> <p>All SimpleLogin certificates are issued by Letsencrypt.</p> Hardenize reports <p>Hardenize is a comprehensive security tool that provides assessment of web site network and security configuration.</p> <p>Here are Hardenize reports for our domains:</p> <ul> <li></li> <li></li> <li></li> <li></li> </ul> Mail Servers <p>Currently SimpleLogin has 2 mail servers located at</p> <ul> <li> (Germany datacenter) and</li> <li> (Netherlands datacenter).</li> </ul> <p>Our mail servers support the following security standards.</p> SPF <p>SPF(Sender Policy Framework) is a protocol that allows domain name owners to control which internet hosts are allowed to send email on their behalf.</p> <p>By default, only our mail servers can send emails on behalf of SimpleLogin. We use the <strong>strictest</strong> SPF policy which is <code>-all</code>. Without SPF, anyone can send emails that seem to come from SimpleLogin.</p> DKIM <p>DKIM (Domain Keys Identified Mail) is an email authentication technique that allows the receiver to check that an email was indeed sent and authorized by the owner of that domain. This is done by giving the email a digital signature.</p> <p>All emails sent from SimpleLogin servers, including emails forwarded to your mailbox and emails sent from your mailbox are DKIM-signed.</p> DMARC <p>DMARC is an email-validation system. It is designed to give email domain owners the ability to protect their domain from unauthorized use, commonly known as email spoofing.</p> <p>Built around SPF and DKIM, a DMARC policy tells the receiving mail server what to do if neither of those authentication methods passes.</p> <p>SimpleLogin uses a strict DMARC policy that rejects emails that fail the SPF or DKIM check.</p> Email TLS <p>Emails sent to our servers are encrypted using TLS 1.1, 1.2 or 1.3. Network attackers can’t uncover what is being communicated, even when they can see all the traffic.</p> Others <p>In addition to the above standards, SimpleLogin mail servers also implement the following recommended standards:</p> <ul> <li>MTA-STS</li> <li>TLS-RPT</li> <li>DANE</li> </ul> Web Servers <p>SimpleLogin currently has 2 web servers located at</p> <ul> <li> (Germany datacenter) and</li> <li> (Netherlands) as failover.</li> </ul> <p>All data is encrypted via SSL/TLS when transmitted from our servers to your browser.</p> <p>In addition, we also implement the following measures:</p> <ul> <li>Only support TLS v1.2 and v1.3. TLS v1.3 supports Forward Secrecy.</li> <li>Do not support previous versions (SSL, TLS 1.0, TLS 1.1) that are deprecated.</li> <li>DANE, HSTS, CSP, SRI, Expect CT, X-Frame-Options, XSS Protection</li> </ul> <p>We take reasonable security measures such as password protection, two-factor authentication for internal logins, and a whitelist of people who can deploy changes to the server. Our web app does not serve any 3rd party hosted JavaScript, except a script from Paddle, our payment processor.</p> Database &amp. File Storage <p>Currently our database and file storage system are hosted in AWS Paris datacenter. The database is using Postgresql, is encrypted at rest and backed up everyday. Backups older than 7 days are deleted. The database is only accessible from our mail and web servers.</p> <p>File storage is based on S3 which is used to store user profile pictures and temporary bounced emails. The bounced emails are deleted after 7 days.</p>

On 2021-02-03 22:47:14 UTC, System (21311) Bot wrote:

Document has been crawled
Old length: 0 CRC 0
New length: 5148 CRC 496613937

On 2022-01-25 09:06:39 UTC, ChristinaAngulo (26253) wrote:

Glad to have the information online about the security system would be wise. I was looking for supportive suggestions happy to have them on your blog. I would like to share blog with others to avail the right help for them. Please continue with wise suggestions must visit for more.