| Blog | https://www.freddieleeman.nl |
| @freddieleeman | |
| Project | https://learnDMARC.com |
| Project | https://URIports.com |
| Project | https://SmartHomeGeeks.io |
At the start of December 2025, Google quietly made a meaningful change to the SPF record published at _spf.google.com. While the change may look subtle at first glance, it has clear benefits for anyone relying on Google in their own SPF configuration. A short history of Google’s
The new BIMI lps= tag, also known as the local-part selector, has been added to the BIMI specification. It allows domain owners to define different brand indicators based on the sender address (for example noreply@, support@, marketing@), without relying solely on the selector header.
With lps=, brands can assign unique BIMI logos to different sender types, exclude certain local-parts from showing any logo at all, and gain far more control over how their brand appears in recipients’ inboxes.
https://www.uriports.com/blog/bimi-lps-tag/
#BIMI #EmailAuthentication #DMARC #BrandProtection #URIports #EmailSecurity
The BIMI specification continues to evolve, and one of the most notable changes in draft version 11 is the introduction of the new lps= tag, also known as the local-part selector. What is the lps= tag? In prior versions of BIMI, published brand indicators and their DNS assertion records relied
@cybertrapped If you paste headers into LearnDMARC, we will visualize them for you, but do not check if they are valid. Please note that these headers may not be compliant with DMARC or SPF specifications. For example, when manually checking SPF for IP 192.184.11.189 on the domain abm.com, the result should be a permerror due to excessive void DNS lookups.
Received-SPF: permerror (abm.com ... _spf.salesforce.com: Maximum void DNS look-ups limit (2) exceeded) envelope-from="[email protected]"; client-ip=192.184.11.189
The Penguin of Evil