[ Sending-service guides ]

Authenticate email sent through 1-Grid: configuration and verification

Identify the 1-grid email product and obtain account-specific DNS values before changing authentication.

By the EmailAuth research team · 4 min read

[ Key points ]

  • Identify the exact 1-grid product and authoritative DNS service.
  • Obtain account-generated values rather than copying a malformed example.
  • Verify mailbox and application routes independently.
On this page
  1. Key points
  2. Takeaway
  3. By role
  4. Frequently asked questions
  5. Sources
  6. Glossary
  7. Related guides

[ Takeaway ]

Verify mailbox and application routes independently.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Keep operational evidence

Use the correct product branch, preserve the shared SPF policy and verify each sending route at a controlled recipient.

Next steps

  1. Use the correct product branch, preserve the shared SPF policy and verify each sending route at a controlled recipient.
  2. Verify the authoritative DNS owner before applying a change.
  3. Save the account-generated selector record.

CISO / SecOps

Review the trust boundary

Require evidence of authorised domain signing and protect private keys. Retire old DNS trust only after confirming all dependencies.

Next steps

  1. Require evidence of authorised domain signing and protect private keys.
  2. Retire old DNS trust only after confirming all dependencies.
  3. Review retired account and selector dependencies.

Founder / Non-technical

Own the business decision

Assign ownership across the email product and DNS provider. Ask for confirmed configuration rather than treating an internet example as a deployable record.

Next steps

  1. Assign ownership across the email product and DNS provider.
  2. Ask for confirmed configuration rather than treating an internet example as a deployable record.
  3. Confirm any advanced-support quote.

[ FAQs ]

Frequently asked questions

Does this guide assume every 1-grid account uses cPanel?

No. Identify Professional Email Basic or Pro versus the actual hosting control panel and outbound service first.

1-grid: DNS settings for Email Basic or Pro

Can I paste the Professional Email SPF example?

Not literally. The cited example contains placeholders and formatting concerns. Obtain account-confirmed values and validate the complete policy.

1-grid: DNS settings for Email Basic or Pro

Where do my DKIM values come from?

From the actual product’s domain-signing configuration or provider support. Confirm both the public DNS value and that signing is enabled.

1-grid: DNS settings for Email Basic or Pro

Why is cPanel Repair unavailable?

cPanel documents that Repair is unavailable when it does not control the domain’s DNS. Publish the reviewed values through the authoritative operator.

cPanel: Email Deliverability

Should I add another SPF record for 1-grid?

No. Preserve one valid policy at the relevant owner and merge only the required authorised sending mechanisms.

Does aligned DKIM make an unrelated SPF domain aligned?

No. They remain separate paths, although one passing aligned DKIM path can satisfy DMARC.

Has this article tested my account?

No. It is documentary guidance with a synthetic identity example. Run controlled tests through your actual mailbox and application routes.

Will support perform every DNS change for free?

Do not assume that. The provider distinguishes standard guidance from advanced work; confirm scope and any quote before commissioning it.

1-grid: scope of support

[ Sources ]

Sources

  1. 1-grid: DNS settings for Email Basic or Pro

    Sections DNS Record Types for Professional Email · Setting Up DKIM · Step-by-Step DNS Update Flow

  2. 1-grid: scope of support

    Sections Standard Support (Included) · Advanced Support (Paid Services)

  3. cPanel: Email Deliverability

    Sections Email Deliverability table: Repair · Manage the Domain: DKIM and SPF

  4. RFC 9989: DMARC

    Sections §4.4 Identifier Alignment Explained · §5 DMARC Policy

  5. RFC 7208: SPF

    Sections §4.5 Selecting Records · §4.6 Record Evaluation

  6. RFC 6376: DKIM

    Sections §3.5 The DKIM-Signature Header Field · §3.6 Key Management

[ Glossary ]

Glossary

Aligned authentication
A passing SPF or DKIM identity that meets the applicable relationship to the visible From domain.
Authoritative DNS
The DNS service responsible for publishing records for a zone.
Evidence boundary
The scope of what the cited documentation or a particular test can establish.

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

Knowledge Base