Domains for Jericho simulation allowlisting
Use this reference with your email provider’s guide. It covers the shared domains for standard Jericho simulation delivery. Custom domains and other delivery methods may require different values; confirm those with Jericho Support.
Last verified: November 16, 2026.
Choose the right domain values
Section titled “Choose the right domain values”| Rule you are configuring | Values to use |
|---|---|
| Sender rule matching the visible From address | The sending domains in the first column below, or the full sender address if the rule requires one. |
| DKIM-based rule, including Microsoft 365 Advanced delivery | The corresponding DKIM domains in the second column below. |
| Envelope sender (MAIL FROM) rule | Confirm the actual MAIL FROM value for the delivery method. The shared sending identities below do not have custom MAIL FROM domains configured. |
| URL or web-filter rule | The link and tracking domains in the URL section below, scoped according to your provider’s guide. |
Apply the entries needed for your selected campaigns. If your organization uses the full shared sender catalog, use the complete relevant column where your provider supports it. Pair domain conditions with the dedicated sending IPs where supported. Separate allowlists do not necessarily combine their conditions.
Shared sending and DKIM domains
Section titled “Shared sending and DKIM domains”These 37 sending domains are covered by 23 verified, DKIM-enabled sending identities. Several sending subdomains share a parent DKIM identity, so the two columns are not interchangeable. For example, a campaign using benefits.age.eu.com is covered by the age.eu.com identity. See AWS’s explanation of DKIM inheritance.
| Sending domains | DKIM domain |
|---|---|
0m365-support.com | 0m365-support.com |
0m365.com | 0m365.com |
age.eu.com, benefits.age.eu.com, prime.age.eu.com | age.eu.com |
amaz0n-support.org | amaz0n-support.org |
do-not-click.net | do-not-click.net |
docsign.cloud | docsign.cloud |
en-delta.com | en-delta.com |
gym-lifetime.life | gym-lifetime.life |
ism.lat, optim.ism.lat, professional.ism.lat | ism.lat |
productiv.ity.co.com, secur.ity.co.com, visibil.ity.co.com | ity.co.com |
visibil.ity.com.co | ity.com.co |
jrchscrty.com | jrchscrty.com |
develop.ment.co.com, invest.ment.co.com | ment.co.com |
mro.cip.us.org | mro.cip.us.org |
nerc.cip.us.org | nerc.cip.us.org |
busi.ness.center, ness.center, well.ness.center | ness.center |
npcc.cip.us.org | npcc.cip.us.org |
rnicrosoftgroup.cc | rnicrosoftgroup.cc |
serc1.cip.us.org | serc1.cip.us.org |
freight.ship.us.org, global.ship.us.org, ship.us.org | ship.us.org |
texasre.cip.us.org | texasre.cip.us.org |
collabora.tion.com.co, educa.tion.com.co, founda.tion.com.co, tion.com.co | tion.com.co |
xn--rfrst-0sa.com | xn--rfrst-0sa.com |
Enter domain names without http://, https://, or an email username in fields that accept domains. Keep xn--rfrst-0sa.com in its ASCII (Punycode) form. A field that requires a full sender address still needs the campaign’s complete address.
For Microsoft 365, use the DKIM domain column in Advanced delivery > Phishing simulation > Domain, together with the sending IPs. These are not custom MAIL FROM values. Confirm the DKIM signing domain in a pilot message’s authentication details if your message takes a different delivery path.
Link and tracking domains
Section titled “Link and tracking domains”Sender allowlisting does not configure URL inspection. Use these hostnames when your gateway or web filter requires a simulation URL exception, following your provider’s instructions.
Application tracking and redirects
Section titled “Application tracking and redirects”app.redirectingly.comShort links
Section titled “Short links”The standard short-link configuration can select from these eight domains:
age.eu.comism.latity.acity.co.comment.co.comness.centership.us.orgtion.com.coA campaign configured to use its own domain can use that hostname instead. Review a pilot message’s links and redirects to confirm any additional campaign-specific values. A hostname appearing in this URL list does not by itself make it a sending domain.
For Microsoft 365 email simulations, Simulation URLs to allow is not required when Advanced delivery identifies the message. Follow the Microsoft 365 guide instead of adding every hostname to that field.
Verify your configuration
Section titled “Verify your configuration”- Select the sender or DKIM values required by your provider, and add the dedicated sending IPs for standard delivery.
- Apply URL exceptions only in the protection layers that require them. Direct Mail Injection does not use the SMTP sending IPs, but simulation links can still be inspected.
- Send a pilot simulation to designated test recipients. Confirm delivery, the signing domain, and the link/redirect hostnames. Check whether scanners create clicks before a recipient interacts with the message.
- Recheck the lists when your campaign domains or delivery method change. Contact Jericho Support for custom-domain values or unexpected differences in the pilot.