Liongard Ideas Portal

Submit and upvote ideas to make Liongard better. You get 20 votes so vote wisely. 🙂

The Product Team is constantly reading your ideas and while we can’t promise that all ideas will become a reality, we value your feedback and promise to always have our Partners in mind when building and improving Liongard.

Check out our FAQs to learn more.

See what we've shipped by clicking here!

Default Selectors for DKIM

Until the last release, the DKIM Selector List was pre-populated with default entries for common mail services. This default list was removed in the last release requiring manual configuration of each domain. This GREATLY reduces the usefulness of this reporting as it requires by-hand configuration of this monitor for every single environment.

I'd like to either see the default selectors return, or an option to configure our own default list that would be applied to ALL environments to monitor.

  • John Hilb
  • Mar 9 2021
  • Future Consideration
Last Reviewed Date 2022-01-07
  • Mar 9, 2021

    Admin response

    Liongard removed these short-lived pre-populated DKIM selectors because they inadvertently created large volumes of false positive in alerting and metrics. The idea is to allow partners to input the selectors unique to their services, thus allowing for more accurate metrics and alerting capabilities. If you add the selector a single time to your respective inspectors, Liongard can then inspect them on a scheduled basis for you. Additionally, with change detection and custom metrics, you can easily track changes and so you know when DKIM may be changed. Our timeline feature will also allow you to know what it used to be just in case it was changed on accident.

    Liongard is also actively looking into bulk changes as well. More to come!

  • Attach files
  • Derek Gabriel commented
    29 Jun, 2021 05:31pm

    Is this why I'm now receiving errors that there is no DKIM configured for many of the domains? Because you removed all the default selectors? That's a poor decision. Instead you should simply auto detect DKIM by using a list of "default" keys that major servies use, if we have an Office 365 inspector, then you should know that "selector1" and "selector2" should be present. Also, it's a very important best practice to have DKIM enabled, if you're using a default list, people should be getting alerts that it's not enabled if it's not enabled. False alerts that it's not enabled when it is enabled is not helping anyone.