DMARC Records not specified your email authentication can be bypassed

Tue Jun 16 13:02:06 EDT 2015

<html>
<body>

    <h1>DMARC Records not specified your email
authentication can be
bypassed</h1><br><br><pre>Your SPF record is 

`None`
Which very well shows that you don't want
**spoofed** email to be sent from your domains,
but you just forget one thing: 

DMARC is designed to give receivers of email
better judgement control  based on sending domain
reputations.  It provides a platform where the
sending side can publish policies to improve
effectiveness against spam and phishing, in effect
building domain reputations. This helps to provide
guidelines on how to address messages that do not
align according to those policies published by the
sending domains.

DMARC was aimed at:

Reducing false negatives
Provide authentication reporting
Apply sender policies at the receiving end
Reduce phishing
Be scalable

In order to get started with DMARC, the sending
domain needs to have an SPF and DKIM record
published. Once the SPF and DKIM records are in
place, you can ure DMARC by adding policies to
your domain's TXT records (the same way in which
you published your SPF and DKIM records).  Your
TXT record name should read something similar to
"_dmarc.your_domain.com."  Please replace the
"your_domain.com" with your own domain.

As DMARC policies are published as TXT records, it
defines what an email receiver should do with
non-aligned mail it receives.

You can read more about creating DMARC records and
their uses here:
https://support.sendgrid.com/hc/en-us/articles/200182958-Everything-about-DMARC-
_________________________________________________________________________________________________
**Why should you implement this**

When I try to send a spoofed email from your
domain to anyone like from `support at pidgin.im to
`abcd at example.com`

They get the simple spoofed message which shows no
sign of fakeness to any normal user.

Like this :
http://ultraimg.com/images/d6b0014396d3.png

But when a domain has DMARC record then they get
this 

	http://i.gyazo.com/59c6acf761ff010bb16aa93d19c6fc39.png

The main point here is that DMARC prevents
spoofing by adding this line:

>It has a from address in mailjet.com but has
failed mailjet.com's required tests for
authentication.

Now, thats how DMARC comes to rescue

_____________________________________________________________________________________________

The following site
https://dmarcian.com/dmarc-inspector/pidgin.im

Give the follwong detail:
No DMARC record published.

Which shows that you are missing this security
feature.

You should publish a valid DMARC record for your
domain to prevent any misunderstanding and to
prevent hackers from using your email.</pre>

</body></html><br/>DATE:    16/06/2015<br/>HOUR:  
  05:02:06 pm<br/>IP:       127.6.47.129<br/><br/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pidgin.im/cgi-bin/mailman/private/security/attachments/20150616/b981d750/attachment.html>