What are Safari’s security practices to protect data?
We've implemented a wide range of business practices, policies, and technology safeguards to protect your confidential information. Safari offers a Security White Paper explaining our approach to information security and data privacy. If you'd like a copy, please send a request to
support@safarilaw.com.
Do emails sent by the Safari system comply with SPF, DKIM, and DMARC?
Yes, Safari uses proper email protocols to ensure it delivers emails consistently and to avoid being marked as spam, and all Safari-sent emails sent comply with these protocols. Below is more information about each of these email protocols.
What is SPF?
Sender Policy Framework (SPF) hardens your DNS servers and restricts who can send emails from your domain. SPF can prevent domain spoofing. It enables your mail server to determine when a message came from the domain that it uses. SPF has three major elements: a policy framework as its name implies, an authentication method, and specialized headers in the actual email itself that convey this information. The IETF standard 4408 first proposed SPF in 2006 and standard 7208 updated it again in 2014.
What is DKIM?
DomainKeys Identified Mail (DKIM) ensures that your email content remains trusted and hasn't been tampered with or compromised. It was initially proposed in 2007 and has been updated several times, most recently with the IETF standard 8301. The IETF standard 7372 updated both SPF and DKIM in 2014.
What is DMARC?
Domain-based Message Authentication, Reporting and Conformance (DMARC) ties the first two protocols together with a consistent set of policies. It also links the sender's domain name with what is listed in the From: header and also has some better reporting back from mail recipients. It was proposed as an IETF standard 7489 in 2015.
Is there a question that we have not answered? Please send us the question to
support@safarilaw.com, and we will add it to this FAQ.