RubySigDocs
Sign in

DocsDNS & deliverability

Verifying your setup

Send one message, read its headers, and know in a minute whether everything works.

Updated August 29, 2026

Send a test

From a mailbox in your organization, send a short message to an external address you control — a personal Gmail account is ideal, because its header view is clear and labelled.

Open the received message and view the original: in Gmail, ⋮ → Show original; in Outlook on the web, ⋯ → View → View message details.

What a healthy message shows

Gmail summarises the three checks at the top:

SPF:    PASS with IP 2a01:111:f403:…      ← Microsoft's (or Google's) sending address
DKIM:   'PASS' with domain example.com    ← your domain, signed by RubySig
DMARC:  'PASS'

Further down in the raw headers, three lines prove the round trip:

Authentication-Results: mx.google.com;
       dkim=pass header.i=@example.com header.s=rubysig1 …

The selector rubysig1 is RubySig's key for your domain.

Received: from relay.rubysig.com (167.233.237.1)
        by ….mail.protection.outlook.com …

The message came back to your platform from the relay — and was then delivered by your platform, which is the Received: line above it.

X-RubySig-Stamped: yes

The loop guard. Its presence is what told your transport rule (or content compliance rule) not to send the message to RubySig a second time.

And at the bottom of the body, the signature itself.

If something is missing

You see It means Look at
No X-RubySig-Stamped header, no signature The message never went to RubySig The transport rule / compliance rule is disabled, or its conditions do not match this sender and recipient
X-RubySig-Stamped present but no signature RubySig saw the message but has no signature profile for this sender The user is missing from the directory sync, or has no template assigned
Signature present, dkim=none or dkim=fail for your domain The DKIM record is not published or not yet visible DKIM; the portal's Setup page shows the live status
Message never arrived Deferred or refused somewhere in the path Mail deferred
Message arrived many times, or a "too many hops" bounce The loop guard is not in place Mail loops

For Google Workspace, Reporting → Email Log Search in the Admin console shows the same story from Google's side: the compliance rule under Matched rules, delivery to an SMTP server (the relay), and the return. It is the first place to look when a message seems not to have been stamped.