Skip to main content
Ocean AI Response (Sonar) is Ocean’s post-delivery response platform built on an agentic architecture, enabling autonomous detection, investigation, and remediation of email threats. It empowers security teams to act faster and smarter. This DNS setup is required for both AI Response features:

​
Prerequisites

An Admin account on your company’s DNS registrar is needed to complete setup, as it requires adding DNS records.
Before you begin, ensure you have:
  • Administrative access to your company’s DNS provider (Namecheap, GoDaddy, Cloudflare, etc.)
  • Your unique SendGrid subdomain values provided by Ocean

​
Deployment Overview

For Ocean to send AI responses to your employees with a sender from your corporate domain while passing all modern mail-security checks (SPF, DKIM, DMARC), you need to add three CNAME records. Each record delegates a subdomain to SendGrid, which then serves the right keys and settings automatically.

​
IP Allowlisting

To prevent Ocean’s automated responses from displaying an “External Email” warning banner in your organization’s email clients, add the following IP address to your email gateway’s allowlist: 
134.128.105.57
This is Ocean’s static IP address used for sending all AI Response (Sonar) automated responses. Adding it to your allowlist ensures emails from Ocean are treated as internal communications.

​
Setup Steps

​
Step 1: Access Your DNS Provider

Log in to your DNS provider panel (Namecheap, GoDaddy, Cloudflare, etc.).

​
Step 2: Add CNAME Records

Add three CNAME records to your DNS configuration. The Ocean team will provide you with the exact Host/Name and Value for each record specific to your organization.
The table below is only an example. Do not use these values. Contact your Ocean representative to receive your organization’s unique DNS records.
Example format:
TypeHost/NameValue/Points to
CNAMEem1234.yourdomain.comu12345678.wl162.sendgrid.net
CNAMEoc._domainkey.yourdomain.comoc.domainkey.u12345678.wl162.sendgrid.net
CNAMEoc2._domainkey.yourdomain.comoc2.domainkey.u12345678.wl162.sendgrid.net
Record explanations:
  • First record: Establishes the sending subdomain for SPF alignment
  • Second record (oc._domainkey): Primary DKIM signing key
  • Third record (oc2._domainkey): Secondary DKIM signing key for key rotation

​
Step 3: Verify Configuration

Contact your Ocean representative to verify the DNS records have been added correctly. Ocean will confirm that:
  • All three CNAME records are resolving properly
  • SPF, DKIM, and DMARC checks are passing
  • The Phishing Response AI Agent is ready to send emails from your domain

​
Troubleshooting

​
DNS propagation delay

DNS changes can take up to 48 hours to propagate globally, though most changes take effect within a few hours. If verification fails immediately after adding records, wait and try again later.

​
Record not found errors

Ensure you’ve entered the records exactly as provided, including:
  • Correct spelling of subdomains
  • No trailing dots (unless your DNS provider requires them)
  • CNAME type selected (not A, TXT, or MX)

​
Existing conflicting records

If you have existing records for the same subdomains, you may need to remove them before adding the CNAME records. CNAME records cannot coexist with other record types for the same hostname.