Regent Bank: email security grade A

Home › Financial services › Bank Email Readiness Index › Regent Bank

Regent Bank, Tulsa, Oklahoma, is the 543rd largest FDIC-insured US bank by total assets ($2.2bn). On 4 November 2026 the public email records of regent.bank graded A: MX pass, SPF pass, DMARC p=reject, mail handled by Microsoft 365.

Grade A. Nothing in the records will stop mail. Read by DNS on 4 November 2026; the records are shown as published.

What was found on regent.bank

Check	Result	What was published
MX	Pass	`0 regent-bank.mail.protection.outlook.com`. Mail handled by Microsoft 365
SPF	Pass	`v=spf1 include:_u.regent.bank._spf.smart.ondmarc.com include:_spf.elasticemail.com ~all`. DNS lookups: 8 or more of 10 allowed; ends ~all
DMARC	Pass	`v=DMARC1; p=reject; pct=100; aspf=r; fo=1; ri=3600; rua=mailto:cbab9e92@inbox.ondmarc.com; ruf=mailto:cbab9e92@inbox.ondmarc.com;`. Policy p=reject, applied to 100% of mail; reports collected (rua= set)
DKIM	Pass, not graded	Key found on selectors selector1, selector2, k1, s1, s2, resend (of 10 common selectors tried)

Where Regent Bank ranks

Regent Bank is the 543rd largest FDIC-insured US bank by total assets, at $2.2bn as reported to the FDIC (certificate 4160; Tulsa, Oklahoma). Among the 999 graded banks, Regent Bank ranks 369th by grade (ties broken by assets, larger first). In its asset band, $1bn to $10bn, it ranks 254th of 846; among the 22 graded banks in Oklahoma, 8th. 66% of its band and 68.2% of its state graded A.

What this means for the bank

The checker's own notes on each record:

MX, pass: 1 MX record. Replies have somewhere to land. Mail is handled by Microsoft 365.
SPF, pass: One SPF record, ending in ~all (softfail): mail from a server that is not on the list is treated as suspect.
SPF, info: DNS lookups: at least 8 of the 10 allowed. One more sending service could push it over. This count is an estimate.
SPF, info: The record uses SPF macros, which only resolve for a real message, so the lookup count is a floor.
DMARC, pass: Policy p=reject: receivers are asked to refuse mail that fails.
DMARC, info: Reports go to cbab9e92@inbox.ondmarc.com.
DKIM, pass: DKIM key found at selector1._domainkey.regent.bank, about 2048-bit RSA.
DKIM, pass: DKIM key found at selector2._domainkey.regent.bank, about 2048-bit RSA.
DKIM, pass: DKIM key found at k1._domainkey.regent.bank, about 1024-bit RSA.
DKIM, pass: DKIM key found at s1._domainkey.regent.bank, about 2048-bit RSA.
DKIM, pass: DKIM key found at s2._domainkey.regent.bank, about 1024-bit RSA.
DKIM, pass: DKIM key found at resend._domainkey.regent.bank, about 1024-bit RSA.

What this means if you sell to Regent Bank

Regent Bank receives mail through Microsoft 365, whose Exchange Online Protection checks every inbound message's SPF, DKIM and DMARC and scores the sender's reputation. A clean, warmed sending domain is the minimum; a failed check lands in junk or is dropped. Before you send, run your own domain through the email setup checker and publish a policy with the DMARC record generator. For how a bank buys, see the selling to banks playbook.

Check it live

The records above are from 4 November 2026. Run the same check on regent.bank now for today's result. The FDIC's record of the bank is at BankFind, certificate 4160.

This page is one of 1,000 in the Bank Email Readiness Index Q4 2026, published 4 November 2026 and re-read every quarter; the next edition is due 2 February 2027. If you work at Regent Bank and the records have changed, email moe@roimaxi.com and we will re-check and update this page.

ROI Maximizer is a trading name of M Ventures LTD, registered in England and Wales, company no. 15554493. Registered office: 4 Beau Street, Bath BA1 1QY, United Kingdom. moe@roimaxi.com