Domain Intelligence
Last Updated:
Cms Email Verification
Safe to Send
Cms.gov is operated by Centers for Medicare & Medicaid Services. The domain runs 4 mail exchanges and SMTP is responsive, with all three authentication standards in force.
Safe to Send
RISK
5
/100
Low
Disposable
No
Persistent addresses, not throwaway
SMTP Live
Yes
Mail server responds to SMTP handshake
MX Records
4
Mail exchangers
Mail Exchange (MX) Records for cms.gov Mail Exchange records. They tell other mail servers which hosts are responsible for receiving email at this domain, in priority order. Lower priority numbers are tried first.
#10
primary.us.etp.fireeyegov.com 15.200.32.5
Reachable
#20
alt1.us.etp.fireeyegov.com 15.200.32.4
Reachable
#30
alt2.us.etp.fireeyegov.com 15.200.32.6
Reachable
#40
alt3.us.etp.fireeyegov.com 15.200.32.6
Reachable
SMTP Handshake
Simple Mail Transfer Protocol. We open a live SMTP connection to the primary MX and read the greeting banner. A response confirms the mail server is alive and accepting connections.
Responsive
BANNER220 2.0.0 mx.us.email.fireeyegov.com ESMTP
Primary mail server accepted SMTP connection and returned a banner during the live audit.
cms.gov Email Authentication SPF · DKIM · DMARC
SPF
Sender Policy Framework. A DNS record listing which servers are allowed to send mail for this domain. Receivers reject or flag mail from unauthorized servers.
Pass
TXTv=spf1 ip4:15.200.33.0/24 ip4:15.200.32.0/24 ip4:63.88.93.240/28 ip4:158.72.139.19 ip4:158.72.139.19 ip4:146.123.140.0/26 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:104.152.72.100 ip4:158.70.144.146 ip4:65.213.206.111 ip4:65.213.206.112 ip4:65.213.206.113 ip4:208.250.57.111 ip4:208.250.57.112 ip4:208.250.57.113 include:_spf.google.com include:spf.protection.outlook.com include:mail.sandbox2.idp.idm.cms.gov include:_spf.qemailserver.com -all
Authorized senders are defined and pass SPF policy.
DKIM
DomainKeys Identified Mail. The sending server cryptographically signs outbound mail with a private key, and receivers verify the signature using a public key in DNS.
Pass
SELECTORDetected via standard selectors
A DKIM signature was detected. Outbound mail from this domain can be cryptographically verified.
DMARC
Domain-based Message Authentication, Reporting & Conformance. Tells receivers what to do when SPF or DKIM checks fail: none, quarantine, or reject.
Reject
TXTv=DMARC1; p=reject; fo=1; ri=3600; rua=mailto:8idhoybh@ag.us.dmarcian.com, mailto:reports@dmarc.cyber.dhs.gov; ruf=mailto:8idhoybh@fr.us.dmarcian.com;
Strict policy. Receivers are instructed to reject any mail that fails SPF or DKIM. The strongest available setting.
cms.gov Domain Registration WHOIS · Nameservers · Registrar
Registrarget.gov
IANA ID93
RegisteredJune 20, 2001
Last UpdatedSeptember 20, 2025
ExpiresSeptember 15, 2026
Age24 years
TLD.gov
Authoritative Nameservers (6)
- a1-86.akam.net
- a10-67.akam.net
- a13-64.akam.net
- a24-65.akam.net
- a3-66.akam.net
- a8-67.akam.net
Registrant
Hidden by registrar privacy service
Technical Contact
Hidden by registrar privacy service
About this Domain
About cms.gov
The domain cms.gov belongs to the Centers for Medicare and Medicaid Services (CMS), a federal agency within the Department of Health and Human Services. Based in Baltimore, Maryland, CMS administers Medicare, Medicaid, the Children's Health Insurance Program (CHIP), and the Health Insurance Marketplace, serving over 150 million Americans.
As a federal .gov domain, cms.gov complies with CISA Binding Operational Directive 18-01, requiring DMARC, SPF, and DKIM. CMS is heavily targeted by phishing campaigns due to its role in healthcare benefits administration. Fraudulent emails impersonating CMS can be used to steal beneficiary information or conduct healthcare fraud.
CMS mail servers do not operate as catch-all systems. The SMTP infrastructure validates recipients and rejects messages to nonexistent addresses. Given the volume of legitimate correspondence CMS handles, its servers employ greylisting, rate limiting, and connection-level filtering to manage inbound traffic effectively.
Email deliverability to cms.gov requires full authentication compliance. HHS-managed federal email gateways apply comprehensive spam filtering, content inspection, and sender reputation analysis. Senders must maintain valid SPF, DKIM, and DMARC records and a clean sending history for successful delivery to CMS staff inboxes.
Other Domains Similar to cms.gov
Other government email domains we've audited. Click any one to see its MX records, authentication, and risk score.
arizona.gov
State of Arizona
oregon.gov
State of Oregon
canada.ca
Government of Canada
ed.gov
Department of Education
archives.gov
National Archives and Records Administration
dea.gov
Drug Enforcement Administration
illinois.gov
State of Illinois
gouv.fr
Government of France
missouri.gov
State of Missouri
fema.gov
Federal Emergency Management Agency
connecticut.gov
State of Connecticut
gov.za
Government of South Africa
colorado.gov
State of Colorado
whitehouse.gov
The White House
hhs.gov
Department of Health and Human Services
bund.de
German Federal Government
washington.gov
State of Washington
florida.gov
State of Florida
wisconsin.gov
State of Wisconsin
gov.pl
Government of Poland
More Email Verification Tools
Free single-address checks, bulk uploads, and APIs for plugging email verification into your own product.
Common Questions About cms.gov
Is cms.gov a disposable or temporary email provider?
No. cms.gov is not a disposable email provider. It is classified as Government Email operated by Centers for Medicare & Medicaid Services and addresses on cms.gov are persistent rather than throwaway. Mail sent to a valid cms.gov mailbox reaches a real recipient.
How do I verify if a cms.gov email address is valid?
The fastest way to verify a cms.gov email address is to use our email checker. Enter any @cms.gov mailbox at the top of this page and our system performs a real-time SMTP handshake against cms.gov's mail servers, confirming whether the mailbox exists, is reachable, and is safe to send to. No email is ever delivered during the check.
Can I check if a cms.gov email exists without sending a message?
Yes. Our real-time email verification API connects directly to cms.gov's mail server, opens an SMTP session, and queries the mailbox using the RCPT TO command without ever transmitting an actual email. The server's response confirms whether the cms.gov mailbox is valid, full, or non-existent. The recipient never receives anything and never sees the check.
What are the MX records for cms.gov?
cms.gov currently publishes 4 mail exchange (MX) records. The primary MX is primary.us.etp.fireeyegov.com, which is the first server contacted when other mail systems try to deliver email to a cms.gov address. The full list with priorities and IP addresses is in the MX Records panel above. MX records tell sending servers where to route email for cms.gov.
Does cms.gov use SPF, DKIM, and DMARC email authentication?
cms.gov enforces all three email authentication standards: SPF, DKIM, and DMARC (policy: reject). This is the gold-standard configuration. It means receivers can verify that mail claiming to come from @cms.gov is genuine, and cms.gov's DMARC policy of 'reject' instructs receivers how to handle messages that fail those checks.
Why do emails to cms.gov bounce or get blocked?
Bounces from cms.gov usually fall into three buckets: the mailbox doesn't exist (5xx user unknown), the inbox is full, or your sending domain isn't authenticated to cms.gov's satisfaction. The fastest fix is to run each address through a free email verifier before you send, and to make sure your own SPF, DKIM, and DMARC are configured correctly so cms.gov's receivers trust you.
How can I verify a large list of cms.gov email addresses?
Our bulk email verifier accepts CSV or TXT uploads with thousands or millions of cms.gov addresses (or any mix of domains). Every address goes through 30+ checks including SMTP existence, cms.gov catch-all detection, role-account detection, and disposable-domain matching. Results typically come back within minutes and previously-failed addresses on your blacklist are reprocessed for free. For continuous high-volume needs, see our unlimited email verification API.
Is it safe to accept signups from cms.gov email addresses?
Yes, with normal hygiene. cms.gov is a legitimate email service and signups from @cms.gov behave like any other real user. Pipe each address through a real-time email verifier API at the moment of signup to catch typos and dead mailboxes, but there is no need to block cms.gov by default.
What email format does cms.gov use for usernames?
Most cms.gov mailboxes follow common patterns like first.last@cms.gov, firstinitiallast@cms.gov, or first@cms.gov, but the actual local-part rules depend on Centers for Medicare & Medicaid Services. The only reliable way to confirm whether a specific @cms.gov address exists is to run it through a free email verification tool. Guessing patterns will produce a high bounce rate and damage your sender reputation.
How is the cms.gov risk score calculated?
The 0-to-100 risk score for cms.gov combines disposable-domain classification, mail-server reachability, MX record presence and depth, SPF / DKIM / DMARC enforcement, DMARC policy strength, SMTP banner response, and domain age. Lower scores mean safer to send to. Disposable domains are pinned at the high end of the scale. The cms.gov score is recomputed on every audit so it always reflects the live state of the domain.
Is cms.gov a valid government email domain?
Yes, cms.gov is a valid official government email domain operated by Centers for Medicare & Medicaid Services. It is used by government employees and officials for official correspondence.
Is cms.gov a disposable or temporary email provider?
No, cms.gov is not a disposable or temporary email provider. It is an official government domain used for legitimate government communications and operations.
What mail server does cms.gov use?
cms.gov uses mail servers managed by Centers for Medicare & Medicaid Services. Check the MX records section above for specific server details and authentication configuration.
Can I send emails to cms.gov addresses?
Yes, cms.gov addresses accept incoming email. Government mail servers typically enforce strict spam filtering, authentication checks (SPF, DKIM, DMARC), and content scanning. Ensure your sending domain is properly authenticated.
How do I verify an email address at cms.gov?
Use BulkEmailChecker to verify cms.gov addresses. Government domains may have specific SMTP behaviors including greylisting and strict rate limiting. Our tool handles these provider-specific configurations automatically.