Skip to content

Mission 5 · AXIS Launch

Email that lands in the inbox

Your email goes out with your own domain's seal, or through HighLevel's sending until you get a domain, and a test email reached your inbox.

Result

Your email goes out with your own domain's seal, or through HighLevel's sending until you get a domain, and a test email reached your inbox.

Estimated time
50 minutes
Cost
US$ 0 to set up. Every 1,000 emails cost US$ 0.675 from the wallet; a test email costs less than a cent.

Analogy

The notary's seal: it certifies that the email really comes from you.

A letter with a notary's seal doesn't get questioned: the seal certifies who signed it.

Gmail, Outlook and Yahoo do the same with every email: they look for the seal. If an email claims to come from your business and doesn't carry your domain's seal, it goes to spam or gets flagged.

The seal is a few records you add to your domain. Today you add them, or you write down the plan to add them.

Why it matters

Alba sent her first promotion from albastudio.houston@gmail.com, with no domain of her own. Several clients found it in spam, and the ones who opened it saw an odd address from someone else's domain next to the studio's name. Two replied asking if it was a scam. The copy was fine; the seal was missing.

Step-by-step guide

Menu paths are shown as they appear in the English interface, with the Spanish name in parentheses for teams that work in Spanish. In the Spanish interface, Email Services stays in English in the Settings menu; inside, the tab reads «Servicios de correo electrónico» and the button «Dominio e IP dedicados».

  1. Pick your path

    Path 1 · You have your own domain (for example, albastudio.com): you create a sending domain and verify its records.

    Path 2 · You don't have a domain yet: you use HighLevel's sending, which works from day one, and send a test email.

    Key points

    • Without your own domain, HighLevel sends from a shared domain. You'll see it as a card in Settings → Email Services (in the Spanish interface it reads «Dominio compartido»), with a domain such as mail.msgsndrsonline.com.
    • The sending address is rewritten to one on HighLevel's shared domain (its help gives …@mg.msgsndr.com as an example), and your clients see it next to your name.
    • For marketing email, HighLevel recommends a domain you own. Don't use a Gmail or Yahoo address as the sender for your campaigns.
    • Promotions go only to people who agreed to receive them and carry an unsubscribe link; you'll see it in full in I.6.
    • If you take path 2, buying the domain comes in module I.3. Today's lesson leaves you a written plan.

    Source: F4, F2, F6

  2. Path 1 · Create your sending domain

    Settings → Email Services → Dedicated Domain And IP → + Add Domain

    In a Spanish-language account: Configuración → Email Services → Dominio e IP dedicados → + Add Domain

    Inside your sub-account, open Settings → Email Services and choose the Dedicated Domain And IP button.

    A view opens with ← Back to SMTP Service, the Dedicated Domain and Domain Configuration tabs and a + Add Domain button. Choose + Add Domain.

    Enter a new subdomain you don't use for anything else. For example, mg.albastudio.com.

    Choose Add & Verify. HighLevel shows you the records your domain needs.

    If your DNS is on Cloudflare, GoDaddy or Namecheap, HighLevel may offer to set them up automatically. If it does, use it, and on Cloudflare check afterwards that they're set to DNS only.

    Key points

    • The subdomain keeps it from clashing with the email you already use. Your Google Workspace or Outlook email keeps working the same.

    Source: F1, F2, F3

  3. Path 1 · Copy the records into your domain

    Open your domain's DNS zone, wherever you bought or manage the domain.

    Copy each record exactly as it appears on your HighLevel screen: type, name and value. Don't type them from memory or from a tutorial.

    If your provider fills in the domain for you, copy the name HighLevel gives you and remove the ending .albastudio.com. So mg.albastudio.com becomes mg, and abc._domainkey.mg.albastudio.com becomes abc._domainkey.mg.

    If you use Cloudflare, set the records to DNS only, with the gray cloud.

    Your sending DMARC goes on _dmarc.mg, type TXT. If HighLevel shows it in its list, copy it there; if not, add it with the value v=DMARC1; p=none;. Never add a _dmarc on your main domain: if it already has one, leave it alone.

    Key points

    • Your DNS zone is your domain's phone book: each record is a line that tells Gmail where to look something up. Today you add the lines HighLevel gives you.
    • Each record does one part of the seal. SPF lists the servers allowed to send for you, and DKIM signs each email. DMARC says what to do when something doesn't match. MX records receive mail sent to your sending subdomain, and the CNAME makes tracking links show your domain.
    • A name can only have one SPF record and one DMARC record. Because you're using a subdomain, yours go on other names and don't clash with your email's.
    • p=none is monitoring mode: it blocks nothing. Reports only arrive if you add a rua, which you do in lesson I.3.4. Moving to reject too early can block your own email.

    Source: F1, F3, F5, F12

    The five records of the seal
    The five pieces of the seal
    1SPFWho may send
    2DKIMSignature
    3DMARCPolicy
    4MXThe subdomain’s mailbox
    5CNAMELinks
    On a subdomain, such as mg.yourdomain
  4. Path 1 · Verify

    Settings → Email Services → Dedicated Domain And IP → ⋯ → Verify domain

    In a Spanish-language account: Configuración → Email Services → Dominio e IP dedicados → ⋯ → Verificar dominio

    Back in HighLevel, open the three-dot menu ⋯ on your domain's card and choose Verify domain. The same menu has Delete domain, Assign IP, Set Headers, Domain Settings and SMTP Settings.

    Each correct record shows a green check.

    If one fails, wait a few minutes and verify again. Propagation usually takes minutes and sometimes up to 48 hours.

    If a record still isn't verified when you finish the mission, send the test email today and upload the domain screenshot once it verifies.

    Key points

    • Once verified, HighLevel warms up your domain automatically: it starts with a cap of 1,000 emails a day. It moves up a stage only on days you send the full cap. One HighLevel guide says around 4 weeks, but if you send less, you stay in the first stage, and that's fine. Until then, don't send big lists.
    • Your domain's card shows this under Domain Warmup, with its stage (Stage 1 at the start) and how many of the day's 1,000 emails you've sent.

    Source: F1, F2, F9, F11

  5. Both paths · Send a test email

    Marketing → Emails → Templates → (open the template) → Preview → ⋮ → Test Email

    In a Spanish-language account: Marketing → Correos → Plantillas → (abre la plantilla) → Vista previa → ⋮ → Correo de prueba

    Open Marketing → Emails and create a simple template: a greeting and one line.

    Make the subject "Test" plus your evidence code, as in Test AX-7K2Q.

    Inside the template, choose Preview and, from the three-dot menu next to it, Test Email.

    Pick the sender. Path 1: an address on your subdomain, like hello@mg.albastudio.com. Path 2: keep the one your account has; HighLevel rewrites it to an address on the shared domain, which is what your own domain fixes.

    Enter your personal email under Receiver Email and choose Send Test Email.

    Check your inbox. If it isn't there, look in spam or promotions, and write down where it landed.

    Key points

    • Landing in spam doesn't fail the mission: it's information. On path 2, it's exactly what your own domain fixes.

    Source: F10, F11, F2

    Two senders in the inbox
    With the shared domain · path 2
    Alba Studio…@mg.msgsndr.com · address rewritten to HighLevel’s shared domain, next to your name
    With your own domain · path 1
    Alba Studiohello@mg.albastudio.com · exactly as you set it up

Interactive

The five parts of the seal

This interactive is used inside your AXIS account.

  1. 06Build
  2. 07Prove
  3. 08Check
  4. 09Teach it

This happens in your account.

Building, proving, checking and explaining in your own words happen inside your AXIS account, with your personal code and AXIS Tutor at your side.

  • Build. The task in your own HighLevel account, with its “done” criterion.
  • Prove. You upload your evidence and an AI reviews it first.
  • Check. Four questions, each option with its explanation.
  • Teach it. You explain it in your own words.

If it breaks

The mistakes that repeat most, and the way out.

A record won't verify.

If your provider fills in the domain, remove the ending .albastudio.com from each name, or it ends up doubled. Check that the value has no extra spaces or quotes, and wait a few minutes before verifying again.

Source: F1

I use Cloudflare and it won't verify.

Set the records to DNS only, with the gray cloud. With the proxy on, verification fails.

Source: F3

I have two SPF records.

A name allows only one SPF. HighLevel's goes on the sending subdomain; your email's stays on the main domain.

Source: F5

My test email landed in spam.

Write it down: it's your starting point. With your own domain, check that every record is verified and don't send big lists while the domain warms up. Without one, it's the reason to get one.

Source: F11

I don't know where my domain's DNS zone is.

It's wherever you bought or manage the domain (GoDaddy, Cloudflare, Hostinger or another). HighLevel has guides for some providers; otherwise, search your provider's help for "DNS zone."

Source: F3

Date

AXIS by CREZIR · Editorial lead: Daniel Mendoza Arévalo · Verified on October 11, 2026 against the HighLevel Help Center and Google's and Yahoo's sender guidelines

Sources (12)
  1. F1 How to add a domain and verify DNS records · Last modified: June 30, 2026
  2. F2 Dedicated email sending domains: overview and setup · Last modified: April 17, 2026
  3. F3 Setting up whitelabel, email sending and other domains · Last modified: September 10, 2026
  4. F4 What is LC Email? · Last modified: August 20, 2026
  5. F5 Email authentication errors: fix SPF, DKIM and DMARC issues · Last modified: July 1, 2026
  6. F6 Meeting Google and Yahoo sender requirements · Last modified: June 30, 2026
  7. F7 Google · Email sender guidelines · Last modified: sin fecha publicada
  8. F8 Yahoo · Sender best practices · Last modified: sin fecha publicada
  9. F9 Domain warmup: fixed stage model · Last modified: June 30, 2026
  10. F10 Preview and test your email campaign templates · Last modified: September 21, 2026
  11. F11 Email sending guide: best practices and warm-up · Last modified: June 30, 2026
  12. F12 RFC 9989 · Domain-Based Message Authentication, Reporting, and Conformance (DMARC) (IETF) · Last modified: mayo de 2026 (Standards Track; reemplaza a los RFC 7489 y 9091)