Keap uses an internal content-checking system to identify issues that may negatively affect deliverability across mailbox providers and third-party email security systems. This system analyzes your content, URLs, HTML structure, formatting, sending patterns, and multiple spam-detection signals including Apache SpamAssassin.

One of the components used by SpamAssassin is Razor2, a distributed, content-based spam-detection network that can blocklist domains associated with known spam content or risky sending behavior.

What Is Razor2 and How It Impacts Domains

Razor2 does not function like traditional IP-based blocklists. Instead, it maintains a database of content signatures and domain associations observed across global spam activity.

How Razor2 Leads to a Domain Listing

A domain becomes listed when:

• Its URLs appear inside content that matches Razor2 spam signatures, and

• Mail using that domain repeatedly generates negative indicators such as complaints, bounces, or spam-trap hits.

In short:

Content is the root cause of the Razor2 listing. The domain becomes listed because the content sent from that domain resembles known spam and produces negative engagement signals.

Because of this, Razor2 treats the domain as high-risk and flags or blocks messages containing it.

What a Razor2 Domain Listing Means

If a domain is listed:

• Email that uses the domain is flagged as matching known spam patterns.

• Security systems honoring Razor2 may block, quarantine, or filter those messages.

• The domain is considered high-risk due to its association with spam-like content or behavior.

Why Content Still Matters

Even though the domain is what ends up on the Razor2 list, the content and behavior behind that domain are what caused the listing.

Common content factors that trigger a Razor2 domain listing:

• Spam-like phrases or templates

• Reuse of content previously seen in spam campaigns

• Links that redirect, forward, or point to risky sources

• Overly promotional or “spammy” HTML structures

• Repetitive mass-marketing emails with consistently low engagement

• Messages that generate complaints or high bounce rates

Razor2 evaluates a combination of:

• Content signatures

• Associated domains

• User-generated spam signals

…to determine whether a domain becomes listed.

Delisting: Important Note

There is no official or unofficial delisting mechanism for Razor2.

The third party maintaining Razor2’s data now refuses all delisting requests, including those from email service providers.

This means:

• Keap cannot delist a customer’s domain.

• Customers cannot delist their own domain.

• The listing remains until the domain stops appearing in high-risk content at scale.

The only path to improvement is to correct the sending behavior and content that caused the listing.

How Keap Responds to Razor2 Domain Listings

When Keap detects that a customer’s sending domain is listed on Razor2, we take steps to protect the sending network while providing transparency and guidance.

1. Keap Flags the Issue in the Content Check Tool

Keap’s content-checking system will display:

• Razor2 domain-listing warnings

• Indicators showing what part of the content triggered a match

• Content patterns associated with Razor2 signatures

• Recommendations for remediation

This gives users visibility into the issue and clear next steps.

2. Updated Behavior: Users Are No Longer Blocked From Saving Content

Previously:
Keap blocked users from saving or sending emails that contained a Razor2-listed domain.

Updated Policy:

• Keap will still detect when a domain used in content is listed on Razor2.

• Keap will warn the user in the content checker.

• Users will be allowed to save and send the email.

Why This Change Was Made

Because Razor2 has no delisting mechanism, blocking legitimate email content gives users no path forward.
Instead, Keap now focuses on:

• Transparency

• Education

• Clear remediation guidance

This approach helps users fix underlying issues while still protecting their deliverability.

3. Compliance Actions May Still Occur if Risk Is High

If a Razor2 listing results from:

• High spam-complaint volume

• Compromised accounts

• Repeated AUP violations

• Large-scale risky sending behavior

• Very poor engagement

Keap may issue a compliance case (Self-Remediation or AUP Review), depending on severity.

How to Fix a Razor2 Domain Listing

While you cannot delist a domain, you can prevent future problems by correcting the issues that led to the listing.

1. Update and Repair Content

Rewrite messages to avoid Razor2 signature matches:

• Revise promotional copy

• Remove or replace risky links

• Avoid reusing templates or copy that may appear in global spam patterns

• Fix HTML errors, excessive styling, or old code blocks

• Reduce repetitive, boilerplate marketing content

2. Stop Sending Content That Produces Complaints

High complaint rates are strongly tied to Razor2 association.

Recommended actions:

• Pause campaigns generating complaints

• Segment disengaged or inactive contacts

• Clean lists regularly

• Remove purchased, rented, or shared lists

• Ensure opt-in quality and permission compliance

3. Improve Account Security

If the domain was listed due to compromised sending:

• Reset passwords

• Enable MFA

• Audit outbound automations

• Remove unauthorized integrations

• Review sending logs for suspicious activity

Summary

• Razor2 lists domains when their content and sending behavior match known spam signatures.

• The content, not the domain itself, is usually the cause of the listing.

• Keap now allows saving and sending of emails using Razor2-listed domains but provides strong warnings and guidance.

• There is no delisting path, so improvements must come from fixing content and sending practices.

• Keap may still take compliance action if the associated risk is high.