Results for s6005b748@go.scanmy.email

General email informations

Sent at 2020-05-09 13:47:08
Received at 2020-05-09 13:47:08 UTC (0 seconds)
SMTP server IP 10.11.12.13
SMTP Reverse DNS (PTR) p12o13.example.com
EHLO Ok p12o13.example.com
SMTP client protocol Ok Email received via ESMTP using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (recommended)
SMTP FROM ushfhgsrth235vfsrthsrth@bounce.example.com
Header FROM Simon <simon@example.com>
Subject My beautiful test
Content

IP informations

Sending IP 10.11.12.13
ISP owner Example SAS
Usage type Data Center/Web Hosting/Transit
Country France
Senderscore 94 Good ! More infos about Senderscore
AbuseIPDB score 4 Good ! More infos about AbuseIPDB
Blacklisted on 1 impacting blacklists for 10.11.12.13
0spam DNSBL ok
Barracuda BRBL ok
Lashback UBL ok
Manitu NiX Spam ok
NoSolicitado BL listed
PSBL Passive Spam Block List ok
Return Path RPBL ok
SORBS Aggregate zone ok
SpamCop Block List ok
Spamhaus ZEN Combined Block List ok
SpamRATS! RATS-Dyna ok
SPFBL DNSBL - Bad Reputation ok
Truncate DNSBL ok
UCEPROTECT Level 1 ok
UCEPROTECT Level 2 ok
WPBL Block List ok
Zero Spam Project DNSBL ok

Authentication results

SPF test pass for bounce.example.com using 10.11.12.13 (sender SPF authorizedusing mechanism "include:spf.example.com")
DKIM test pass Signed by : dkim-esp.com using sha256 algorithm and a 1024 bits RSA key size
DMARC test pass
SPF test pass
SPF alignment pass
DKIM test pass
DKIM alignment fail
BIMI display No BIMI record found, you may be interested by that new technology to display your logo in front of your emails received. (More infos about BIMI)

Header domains alignment

Header From domain example.com is aligned with bounce.example.com SMTP FROM domain
Header From domain example.com is aligned with p12o13.example.com PTR domain (reverse DNS of sending IP)
Header From domain example.com is not aligned with dkim-esp.com domain(s) used to DKIM sign
SMTP FROM domain bounce.example.com is not aligned with dkim-esp.com domain(s) used to DKIM sign

DNS configurations

SPF validDNS lookups: 7
bounce.example.com SPF record: "v=spf1 include:spf.example.com include:_spf.google.com include:aspmx.pardot.com -all"
DMARC invalid dmarc.example.tech does not indicate that it accepts DMARC reports about example.com - Authorization record not found: example.com._report._dmarc.dmarc.example.tech IN TXT "v=DMARC1"
DMARC location: "example.com"
DMARC record: "v=DMARC1; p=reject; sp=reject; pct=100; fo=1; adkim=r; aspf=r; rua=mailto:dmarc@example.com,mailto:example@dmarc.example.tech; ruf=mailto:dmarc@example.com,mailto:example@dmarc.example.tech"
DKIM configuration dkim-esp.com is using a 1024bits RSA key, which starts to be considered weak (but not vulnerable, a 1024bits key is still safe), you should consider moving to a 2048bits key if technically possible: https://tools.ietf.org/html/rfc8301#section-3.2
DNSSEC DNSSEC protocol is not activated on example.com, more infos on https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en

Content analysis

Rspamd v3.0 some issues found5.79 / 15
2 HTML_SHORT_LINK_IMG_1 Short html part (0..1K) with a link to an image
1.5 URIBL_GREY uribl.com grey url
1 URI_COUNT_ODD Odd number of URIs in multipart/alternative message
0.7 MANY_INVISIBLE_PARTS Many parts are visually hidden
0.5 ZERO_FONT Zero sized font used
0.1 BAD_REP_POLICIES Contains valid policies but are also marked by fuzzy/bayes/surbl/rbl
0.1 RCVD_NO_TLS_LAST Last hop did not use encrypted transports
0 ARC_NA ARC signature absent
0 ASN ["asn:200069, ipnet:87.253.232.0\/21, country:FR"]
0 DKIM_TRACE DKIM trace symbol
0 DMARC_POLICY_ALLOW DMARC permit policy
0 DWL_DNSWL_NONE Message has a valid dkim signature originated from domain listed at https://www.dnswl.org, no trust
0 FROM_HAS_DN From header has a display name
0 FROM_NEQ_ENVFROM From address is different to the envelope
0 MID_RHS_MATCH_FROM Message-ID RHS matches From domain
0 MIME_TRACE ["0:+","1:+","2:~"]
0 RCPT_COUNT_ONE One recipient
0 RCVD_COUNT_ONE Message has one Received header
0 RWL_MAILSPIKE_GOOD From address is listed in RWL - good reputation
0 R_DKIM_ALLOW DKIM verification succeed
0 R_SPF_ALLOW SPF verification allows sending
0 TAGGED_FROM SMTP from has plus tags
0 TO_DN_NONE None of the recipients have display names
-0.01 HAS_LIST_UNSUB Has List-Unsubscribe header
-0.1 MIME_GOOD Known content-type
Spamassassin v3.4.2
Vanilla installation
good0.9 / 5
1.1 URIBL_GREY Contains an URL listed in the URIBL greylist [URIs: exple.com]
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid
0 HTML_IMAGE_RATIO_06 BODY: HTML has a low ratio of text to image area
0 HTML_MESSAGE BODY: HTML included in message
0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3) [10.11.12.13 listed in wl.mailspike.net]
0 RCVD_IN_MSPIKE_WL Mailspike good senders
0 SPF_HELO_PASS SPF: HELO matches SPF record
0 SPF_PASS SPF: sender matches SPF record
0 T_KAM_HTML_FONT_INVALID BODY: Test for Invalidly Named or Formatted Colors in HTML
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain
-0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain
Domains 4 domain(s) extracted 4 issue(s) found
  • 2 domain(s) listed on URIBL
  • 0 domain(s) listed on Abusix
  • 0 other blacklists on domain(s)
  • 2 known tracking domain(s)
    • w3.org
      • URIBL listing: ok
      • Abusix listing: ok
      • Other listing:
      • Tracking domain: no
    • exple.us
      • URIBL listing: listed Greylisted, see http://lookup.uribl.com/?domain=exple.us
      • Abusix listing: ok
      • Other listing:
      • Tracking domain: yes
    • exple.com
      • URIBL listing: listed Greylisted, see http://lookup.uribl.com/?domain=exple.com
      • Abusix listing: ok
      • Other listing:
      • Tracking domain: yes
    • example.com
      • URIBL listing: ok
      • Abusix listing: ok
      • Other listing:
      • Tracking domain: no
Tracking 13 unique external ressources 9 cookies or ETags

Etag and Cookies can be negatively seen, as user tracking inside a mail

  • https://www.example.com/images/theme/v1/icons/ico-social/facebook.png
    • etag: "e5a9b4b55e9bd9d7b38740522c07e693"
  • https://www.example.com/images/theme/v1/icons/ico-social/twitter.png
    • etag: "31d0e7e4fd11515f132671528637f91e"
  • https://www.example.com/images/theme/v1/icons/ico-social/instagram.png
    • etag: "b2db7d7d4b4cd1e6e39abfb45dc7de48"
  • https://www.example.com/images/theme/v1/icons/ico-social/flickr.png
    • etag: "6aa3db15bc21f9c1ca7387f2ffc86623"
  • https://www.example.com/images/theme/v1/icons/ico-social/medium.png
    • etag: "9452c940983c6df34cef935c255f618c"
  • https://www.example.com/images/theme/v1/icons/ico-social/snapchat.png
    • etag: "a9b631fd046404d08c9b01da7e181506"
  • https://www.example.com/images/theme/v1/icons/ico-social/linkedin.png
    • etag: "0e1b4e011e0e82bbe538cdcd5c117f32"
  • https://www.example.com/images/theme/v1/icons/ico-social/pinterest.png
    • etag: "a40a3ce386d2edb0eccbaf71fa05eab9"
  • https://www.example.com/images/theme/v1/icons/ico-social/tumblr.png
    • etag: "f7c09bd91af6c9b11f1d082b186584fb"