Checklist IP Platform Certification

    This checklist helps you assess whether your email sending platform meets the essential terms and conditions and criteria for IP platform certification. It provides an initial overview — for further details, please refer to the linked documents.




    Terms and Conditions

    Basic Participation Requirements

    1.2

    The company operates and fully controls the technical platform for sending commercial bulk emails.

    1.2

    At least three months of sending history are available.

    2.2.1

    All sending IP addresses can be fully identified.

    2.2.2

    Infrastructure is used exclusively for commercial bulk email sending.

    2.2.5

    Proof of responsibility and technical control of the sending servers (via DNS token or WHOIS) is possible.

    2.2.6

    PTR and FQDN entries are configured correctly and unambiguously.

    Criteria

    1.1 Trust and Transparency

    1.1.1

    Postal address and digital contact options (email or contact form) are easy to find on the website.

    1.1.2

    Transparent data protection information on data processing is available on the website.

    1.1.3

    RFC-compliant email format and SMTP communication are ensured.

    1.2 Abuse Prevention

    1.2.1

    An abuse role account is available under the organisation's domain. A 24-hour response following notification on business days is possible.

    1.2.2

    For email sending platform providers: Mechanisms for enforcing CSA criteria are applied, for example rate limiting, blocking, or volume limits.

    1.2.3

    For email sending platform providers: Customer accounts are protected against misuse, for example through 2FA.

    1.2.4

    Redirect links can be deactivated within 24 hours of notification in the event of misuse, for example phishing.

    1.2.5

    Implementation of the "X-CSA-Complaints" header including DKIM signature is possible.

    1.2.6

    Technical security measures are in place for mail servers, for example no open relay, no backscatter, and monitoring.

    1.2.7

    Emails are sent exclusively via current TLS-secured connections.

    1.3 Authentication

    1.3.1

    SPF entries are configured with "-all" or "~all".

    1.3.2

    Emails are sent with a valid DKIM signature.

    1.3.2

    DKIM contains at least the header elements From, Date, and To.

    1.3.2

    The DKIM parameter "l=" is not used.

    1.3.3

    The "d=" tag of the DKIM domain is correctly assigned – either the customer domain (for platform providers) or the sender's own domain (for own senders).

    1.3.3

    There is at least one "relaxed" DKIM alignment with "Header-From".

    1.4 List Hygiene

    1.4.1

    The email sending platform offers list unsubscribe functionality including one-click unsubscribe (POST HTTPS, RFC-compliant) and list help header functionality.

    1.4.2

    A functioning unsubscribe option without login is included in every commercial email of an advertising nature, for example via link or email. This requirement does not apply to transactional emails.

    1.4.3

    For email sending platform providers: An unsubscribe link is available as a platform functionality.

    1.4.4

    Bounce processing in accordance with RFC 5321 is possible.

    1.4.5

    Sending to non-existent recipients is prevented.

    1.5 Reputation

    1.5.4

    The sender's reputation with participating CSA mailbox and security providers is in good standing.

    Your information will be treated confidentially.

      Get in touch with us