Skip to content
Take your AXIS Score Log in ES
Take your AXIS Score

Lesson · Identity and domains

DNS for non-technical people

Your domain is in your name, you know where its records are edited and what each one says, and you've written your first line in its directory.

Build it in your accountI already have access: sign in

Result

Your domain is in your name, you know where its records are edited and what each one says, and you've written your first line in its directory.

Estimated time
35 minutes
Cost
US$ 0 if you already have a domain. If not, you pay your registrar: a .com renews at US$ 10.46 at Cloudflare and US$ 22.99 at GoDaddy, as of 12 Oct 2026. On 1 Nov 2026 the wholesale price goes up US$ 0.71.

Analogy

The sign and the business address.

Your domain is your business address: it's how people find you, on the web and by email.

DNS is the phone directory that says where everything at that address is: the storefront, which is your website, and the mailbox, which is your email.

The registrar is the office where you registered the address and where you renew it every year.

The nameservers say which directory is the official one: only what you write in that directory counts.

In this module you put up your sign, your shop window and the seal on your letters. Today you learn to read the directory and write your first line in it.

Why it matters

The domain albastudio.com goes back two years, to when a freelancer built Alba's first page in Houston. To move fast, he bought it with his own account, and the renewal notices go to him. In mission 5, the freelancer pasted the sending records for her; Alba doesn't know in which panel. Now HighLevel will ask for more records, and she isn't even sure the domain is hers. Today you read your domain's directory and find out who holds each key.

Step-by-step guide

HighLevel paths are shown as they appear in the English interface. If your team works with the account in Spanish, the Spanish names are in parentheses; HighLevel leaves some labels in English. ICANN Lookup, Google Admin Toolbox and registrar panels use the labels their pages show.

  1. Keep your address in your name

    If you already have a domain, sign in to your registrar account: the company you pay for it every year. If you don't have one, you buy it today; this lesson has no path without a domain.

    Buy or review it from an account in your name or your business's name. Never in your freelancer's name or an agency's.

    If it's in someone else's name, ask them in writing to move it into your name or to an account of yours. If they don't answer, tell AXIS Tutor before you go on.

    Turn on auto-renew and check that the card on file is still valid.

    Leave WHOIS privacy on, which hides your contact details, and leave the transfer lock on.

    Before you pay, compare the renewal price, not the first-year price. Prices as of 12 Oct 2026 are below.

    Turn on two-factor authentication for the registrar account. It's another key to the building: add it to your access register from lesson I.2.3.

    Write down in your record sheet the registrar, the registrant, the expiration date and whether it renews on its own.

    Key points

    • What ICANN says: only the registrant, or a contact they authorize, can start a transfer. If your domain is in someone else's name, your address depends on them.
    • One registrar describes the classic case: the third party who did you the favor of registering it put their own name as registrant instead of yours.
    • Privacy hides your details, but they have to be real. If you don't answer a registrar's question about them within 15 days, it can suspend your domain.
    • The lock shows up as clientTransferProhibited: the registry rejects any transfer until you ask to remove it. Cloudflare, for example, locks domains by default.
    • Auto-renew only charges if your payment method is current. ICANN asks you to keep it that way, and Cloudflare turns auto-renew on for every registration.
    • Prices for a .com as of 12 Oct 2026: Cloudflare, which sells at cost, charges US$ 10.46. GoDaddy charges US$ 2.99 the first year with a new-customer coupon and US$ 22.99 to renew.
    • The .com goes up on 1 Nov 2026: Verisign, which sells it wholesale, moves from US$ 10.26 to US$ 10.97.
    • If you serve Mexico, a .mx costs US$ 23.98 the first year at Namecheap and US$ 58.98 to renew; at Cloudflare, US$ 30.70. A .com.mx at Namecheap is US$ 10.48, then US$ 34.98.
    • At Cloudflare, a .co costs US$ 30 a year, renewals included. A .es starts at US$ 5.29 the first year and renews at US$ 5.71 to US$ 17, depending on the agent.
    • Anyone in any country can register a .co, and anyone can register a .mx or .com.mx, first come, first served. A .es is open to individuals and private entities: confirm the requirements with your agent. Third-party prices come from a price-comparison site; confirm them at your registrar before you pay.
    • If the domain expires, your website and email stop. For a .com, the registrar warns you twice: about a month before and about a week before. After that there's often a grace period and then a 30-day redemption period; at Cloudflare, the grace period is 40 days.
    • After that, the name is released, and ICANN can't give you back an expired domain. Country domains such as .mx, .co or .es set their own rules.

    Source: F25, F26, F27, F28, F29, F30, F31, F32, F33, F34, F40, F41, F42, F43, F44, F45, F46, F47, F48, F49, F50, F51

  2. If you buy it in HighLevel, know what you're signing

    Settings → Domains & URL Redirects → Purchase/Transfer Domain

    In a Spanish-language account: Configuración → Dominios y redirecciones de URL → Purchase/Transfer Domain

    You can also buy inside HighLevel. First, your agency turns on Domain Purchase under Settings → Company, on the Basic Details tab.

    In your sub-account, open Settings → Domains & URL Redirects and look for Purchase/Transfer Domain.

    Type the name you want and check the yearly price. HighLevel's help doesn't publish prices: it says to review the price for the name and term before you pay.

    Before you pay, read what you're signing: HighLevel's Terms make HighLevel the listed registrant, not you.

    If you buy it there, note it in your record sheet as "registrant: HighLevel" with the date you could move it out, 60 days after purchase.

    Key points

    • The upside: it comes with WHOIS privacy, a renewal reminder 67 days before expiration, and its DNS is edited inside HighLevel.
    • What you sign: under its June 2026 Terms, HighLevel is the registrant and your agent, with the right to transfer, pause, remove or cancel the domain. The registrar behind it is Cloudflare.
    • It's paid from the wallet for the whole term, and the purchase is final: no refund and no cancellation. Each renewal is charged at the rate in force at that time.
    • You can't change its nameservers while it stays in HighLevel. Once 60 days have passed since purchase, you can transfer it to another registrar or move it to your own Cloudflare account.
    • Turning on Domain Purchase lets every sub-account see the purchase option. If you don't resell it, your agency pays for the domain.
    • What HighLevel requires is that you accept those Terms when you buy. What AXIS recommends: your brand's main domain at an outside registrar, in your name.
    • Keep HighLevel purchases for a secondary or campaign domain, one you could lose without losing your address.
    • In a Spanish-language account, the path starts at «Configuración → Dominios y redirecciones de URL».

    Source: F35, F36, F37, F38, F39, F54

  3. Read your domain's public record card

    Open lookup.icann.org in your browser. It's ICANN's public lookup: you don't need an account.

    Type your domain, for example albastudio.com, and search.

    Find the registrar and compare it with the one you noted in step 1: they should match.

    Find the expiration date and the status. If you see clientTransferProhibited, your lock is on.

    Find the nameservers, if the lookup shows them. You'll confirm them with Dig in step 4.

    If a country domain such as .mx, .co or .es returns nothing, open your domain's page in your registrar account. The same details are there.

    Take screenshot 2 with the registrar and the expiration date in view. Cover the registrant's name, email, phone and address, if they appear.

    Key points

    • ICANN Lookup reads the official registration data. Since 28 Jan 2025, the RDAP protocol has replaced WHOIS for generic domains such as .com.
    • No ICANN page says whether the lookup answers for country domains or which fields it shows. That's why you have the registrar-account fallback.
    • If the expiration date is close and your domain doesn't renew on its own, fix it today, before you go on with the lesson.

    Source: F23, F24, F29, F33

  4. Find the official directory: your nameservers

    Open Google Admin Toolbox → Dig, at toolbox.googleapps.com/apps/dig. It's free and doesn't ask you to sign in.

    Type your domain and choose the NS type.

    The answer is your nameservers. Their names almost always say whose they are: your registrar, Cloudflare, Wix or your web host.

    That's where your official directory lives, and where your records get edited. If they point somewhere other than your registrar, editing at the registrar changes nothing.

    Write down in your record sheet where your nameservers live and who can sign in to that panel. If it's a separate account, it also gets two-factor and goes in your access register.

    Key points

    • The registrar is where you pay for the name. The nameservers say where the records get edited. They can be the same company or two different ones.
    • One example: at Namecheap, the records section only appears if the domain uses Namecheap's DNS. If you don't see it, your directory lives with another provider.
    • Nameservers are changed at the registrar. Cloudflare allows up to 24 hours for the registrar to update them, and the change can take up to 48 hours to show everywhere. Before that, copy your whole zone into your record sheet, especially the MX and TXT records.
    • Cloudflare warns that its automatic scan doesn't always find all your records. And if your domain has DNSSEC on, it gets turned off before the switch.
    • If you connected your domain to Wix through its nameservers, Wix holds your directory and your records get edited there. HighLevel says Wix doesn't accept two MX records with the same priority.
    • That's why HighLevel asks you to move the nameservers away from Wix before you use that domain to send email.
    • If you bought in HighLevel, your directory is edited inside HighLevel and its nameservers can't be changed. Cloudflare's grey cloud only applies if your DNS lives on Cloudflare.

    Source: F1, F2, F3, F8, F10, F12, F7, F5, F35, F11

  5. Read your directory line by line

    In Dig, look up your domain with the A type. That's your website's address at the root, written @ in the panel.

    Look up www. plus your domain with the CNAME type. If it answers with another name, www points to that name; if it answers nothing, try the A type.

    Look up your domain with the MX type: that's where your email lands. The server's name usually says who keeps your mailbox, such as Google.

    Run your domain through Check MX, in the same Toolbox. It reviews your MX records and flags common mistakes.

    Look up your domain with the TXT type and find the line that starts with v=spf1. That's your SPF, and there should be only one.

    Look up _dmarc. plus your domain with the TXT type. If the answer starts with v=DMARC1, you have DMARC at the root; if not, note it and add nothing today.

    If you did mission 5 through path 1, also look up mg. plus your domain with the TXT and MX types, and _dmarc.mg. with the TXT type. They should return the SPF and MX records you copied from HighLevel, and the DMARC record you added.

    Write your five-line reading: where you bought it, where the nameservers point, where your website goes, where your email lands, and whether you have SPF and DMARC at the root.

    Key points

    • A takes a name to a numeric address; AAAA does the same for IPv6. CNAME takes a name to another name.
    • MX says where your email gets delivered. TXT is a note others read: your SPF, your DMARC or a service's verification.
    • NS says who keeps your directory, and CAA says who may issue your website's padlock. A CAA record only matters if you already have one; you'll see it in I.3.2 and I.3.3.
    • A name with a CNAME can't have any other record. That's why the root, which already has NS, MX and TXT records, uses an A record.
    • The TTL says how long others may keep a copy of each line. On Cloudflare, "Auto" means 5 minutes; GoDaddy uses 1 hour.
    • One SPF per name: with two, your email checks fail. If a new service asks for SPF at the root, you edit the one that already exists.
    • One DMARC per name too: if there are two, mail servers throw both away.
    • The root's MX and TXT records hold up your email and your verifications. They're never deleted "to clean up": your mailbox would stop receiving.
    • If you took path 2 in mission 5, mg doesn't exist yet. You'll create it with your domain in lesson I.3.4.

    Source: F3, F4, F5, F9, F7, F13, F14, F15, F22, F53

    Who keeps what
    1RegistrarWhere you pay for the name: registrant, expiration, auto-renew, privacy, lock
    2NameserversWhich directory is the official one
    3 · DNS zone
    At the provider the nameservers nameYour registrar, Cloudflare, Wix or HighLevel
    A at @ → website
    CNAME at www → another name
    MX → mailbox
    TXT → notes: SPF, DMARC, verifications
    Read it without signing in
    ICANN LookupUnder the registrar: registrar, expiration and status
    DigUnder the DNS zone: NS, A, CNAME, MX and TXT
    If the nameservers point somewhere else, editing at the registrar changes nothing

  6. Write your first line: the test TXT record

    Go to the DNS panel your nameservers point to and choose to add a record.

    Type TXT. In the name field (Host or Name, depending on the panel), type only axis-test: the panel fills in the domain.

    In the value, type your evidence code, for example AX-7K2Q. Leave the TTL as it is and save.

    If you use Cloudflare, a TXT record is always DNS only: there's no cloud to turn off.

    Wait a few minutes and look up axis-test. plus your domain in Dig, with the TXT type. If you don't see type buttons, type txt: before the name. It should return your code: that's screenshot 1.

    If it doesn't, check that the name is only axis-test and that you added it where your nameservers point.

    Don't touch any other record. Once your evidence is approved, delete axis-test.

    Key points

    • @ is the root. Everywhere else you type only the prefix, such as www, mg, app, book or _dmarc.mg, because the provider fills in the domain.
    • If you type the full name into a panel that fills it in, the name doubles: axis-test.albastudio.com.albastudio.com. Registrars only say to leave the domain out; look up the doubled name in Dig to check.
    • It almost always shows up within minutes. HighLevel says to wait up to 24 hours before you worry. A nameserver change can take up to 48 hours, and Google says up to 72 for a new MX record.
    • When HighLevel gives you records, copy them from your screen, never from a video or a tutorial. In October 2026 its help asks for the A record 162.159.140.166 for sites; a 2023 tutorial still gives 34.68.234.4.
    • On Cloudflare, every record HighLevel has to verify goes on DNS only, with the grey cloud. With the orange cloud, Cloudflare answers with its own addresses and the check fails.
    • Some providers let HighLevel write the records for you with "Authorize". Its list names GoDaddy and Cloudflare, and still Google Domains, which no longer exists; another guide, for the sending domain, adds Namecheap. If it doesn't offer it, you add them by hand.

    Source: F6, F7, F8, F11, F18, F19, F14, F52, F55, F56

  7. Assign your subdomains and fill in your record sheet

    Settings → Domains & URL Redirects

    In a Spanish-language account: Configuración → Dominios y redirecciones de URL

    Download the "Your domain record sheet" template and fill in part A with what you noted in steps 1 to 3.

    Fill in part B: where your nameservers live and who can sign in to the registrar and the DNS panel.

    In the part C table, write what you read in Dig: the root, www, the MX records, the SPF and the DMARC.

    Give each subdomain one job: mg for the email from mission 5 and app for the white label in I.3.2.

    links is for the API domain in I.3.2, which puts your address on form and booking links. book, or www, is for your page in I.3.3.

    The root stays with what already works: your current website and your business email.

    In your sub-account, open Settings → Domains & URL Redirects: that's where you'll connect your page in I.3.3. You can also get there from the Domains tab under Sites. Today you just find it.

    Write your five-line reading in the evidence field and upload your two screenshots.

    Key points

    • One job per subdomain has a reason. For sending, HighLevel asks for a unique subdomain used for nothing else.
    • HighLevel also blocks a name that another of its products already uses, such as a site or a branded domain. That check skips email products: you protect mg yourself, with your record sheet.
    • Why not the root: HighLevel warns that many users break their mailbox or website by connecting a root that's already in use.
    • app and links each carry a CNAME to a different HighLevel target, and a name with a CNAME can't hold another record. That's why they go on two subdomains.
    • Today your mission 8 form's public link is https://api.leadconnectorhq.com/widget/form/<ID>. The API domain in I.3.2 puts your address on the links it generates.
    • Keep your record sheet alive: whenever you change something in your directory, write it down with the date.

    Source: F16, F17, F5, F18, F20, F21, F4

    One job per name
    albastudio.comOne job per name
    @Current website and business email: don’t touch
    wwwWebsite
    mgEmail sending · mission 5
    _dmarc.mgSeal on the sending · mission 5 and I.3.4
    appWhite label · I.3.2
    linksAPI domain · I.3.2
    bookHighLevel page · I.3.3
    axis-testEvidence for I.3.1; gets deleted
    Copy the values from your HighLevel screen, never from a video
    Settings → Domains & URL Redirects

Your domain record sheet

Your domain record sheet · [your domain] · Owner: [your name] · Last review: [date]

A. The address
Domain: ______________________
Registrar (where you pay for it): ______________________
Registrant (whose name it's in): ______________________   ☐ Me or my business
Expiration date: ____________   Auto-renew: ☐ Yes ☐ No   Payment method current: ☐ Yes (checked on ____________)
Renewal price: US$ ______ a year (price date: ____________)
WHOIS privacy: ☐ Yes ☐ No   Transfer lock: ☐ Yes ☐ No

B. The directory and its keys
Nameservers (where the directory lives): ______________________
☐ My registrar ☐ Cloudflare ☐ Wix ☐ HighLevel ☐ Other: ____________
Who can sign in to the registrar: ______________________   Two-factor: ☐ Yes
Who can sign in to the DNS panel: ______________________   Two-factor: ☐ Yes
Both accounts are in my access register from lesson I.2.3: ☐ Yes

C. The records (fill it in with what you read in Dig and keep it current)
Name | Type | Points to (value) | Job | Who added it and when
Example: @ | A | [your current website's address] | My current site | My web host, 2024
@ | A | __________ | My website | __________
www | CNAME or A | __________ | My website | __________
@ | MX | __________ | My email (never deleted) | __________
@ | TXT (v=spf1) | __________ | My email's SPF (only one) | __________
_dmarc | TXT (v=DMARC1) | __________ | Root DMARC | __________
mg | TXT (v=spf1) and MX | the ones HighLevel gave you | Sending email (mission 5 or I.3.4) | __________
[selector]._domainkey.mg | TXT (DKIM) | the one HighLevel gave you | Sending signature | __________
email.mg | CNAME | the one HighLevel gave you | Sending tracking links | __________
_dmarc.mg | TXT | v=DMARC1; p=none; | Sending DMARC (mission 5; finished in I.3.4) | __________
app | CNAME | the one HighLevel gives you | White label (I.3.2) | __________
links | CNAME | the one HighLevel gives you | API domain: form and booking links (I.3.2) | __________
book | CNAME or A | the one HighLevel gives you | My HighLevel page (I.3.3) | __________
axis-test | TXT | AX-____ | I.3.1 evidence; delete once approved | __________

D. Rules for this sheet
☐ I copy records from my HighLevel screen, never from a video or a tutorial.
☐ One job per subdomain. The root stays with what already works: my current site and my email.
☐ I never delete the root's MX or TXT records to clean up.
☐ On Cloudflare, anything HighLevel verifies goes on DNS only (grey cloud).
☐ Before I change nameservers, I copy the whole zone here.

Never write passwords, verification codes or card details here. This sheet says where each key is, not the key itself.

Reviewed by: ______________________   Date: ____________

Interactive

Which record is it?

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.
Get your AXIS ScoreI already have access: sign in

If it breaks

The mistakes that repeat most, and the way out.

Dig doesn't show my test TXT record.

Wait a few minutes and look it up again. Check that the name is only axis-test, without your domain, and that you added it in the panel your nameservers point to.

Source: F7

My registrar doesn't show where to edit records.

Your nameservers point to another provider, such as Cloudflare, Wix or your web host. Look up NS in Dig and edit your records there.

Source: F8

My website and my email stopped working on the same day.

Look up your domain in ICANN Lookup or your registrar account. If it expired, renew it today and update your payment method; then turn on auto-renew.

Source: F33

I bought my domain in HighLevel and can't change its nameservers.

Its Terms don't allow it while the domain stays in HighLevel. Edit its records inside HighLevel. To use other nameservers, transfer it to another registrar once 60 days have passed since purchase.

Source: F35

I changed my nameservers and my email stopped arriving.

Your MX or TXT records are missing from the new directory. Copy them from your record sheet exactly as they were and wait: Google warns a new MX record can take up to 72 hours to be recognized.

Source: F14

Date

AXIS by CREZIR · Editorial lead: Daniel Mendoza Arévalo · Verified on October 11, 2026 against HighLevel's Help Center and Terms of Service, ICANN, the DNS RFCs and Cloudflare's documentation

Sources (56)
  1. F1 What is DNS? (Cloudflare Learning Paths) · Last modified: April 23, 2026
  2. F2 What is DNS? | How DNS works (Cloudflare Learning Center) · Last modified: sin fecha publicada (© 2026; consultada el 2026-10-12)
  3. F3 DNS record types (Cloudflare Docs) · Last modified: June 2, 2026
  4. F4 RFC 1034 · Domain Names: Concepts and Facilities · Last modified: noviembre de 1987 (más de 12 meses; sigue siendo el estándar)
  5. F5 How to Set Up Different Domain Types in HighLevel: Websites, Email, WordPress & More · Last modified: September 10, 2026
  6. F6 Connecting Your Domain on GHL: A Guide · Last modified: March 25, 2026
  7. F7 Add a TXT record (ayuda de GoDaddy) · Last modified: sin fecha publicada (© 2026; consultada el 2026-10-12)
  8. F8 How do I set up host records for a domain? (Namecheap Knowledgebase) · Last modified: March 31, 2026
  9. F9 Time to Live (TTL) (Cloudflare Docs) · Last modified: April 16, 2026
  10. F10 Full setup · Set up a primary zone (Cloudflare Docs) · Last modified: July 29, 2026
  11. F11 Proxy status (Cloudflare Docs) · Last modified: April 21, 2026
  12. F12 Pointing vs. name servers: domain connection methods (ayuda de Wix) · Last modified: sin fecha publicada (© 2026; consultada el 2026-10-12)
  13. F13 RFC 7208 · Sender Policy Framework (SPF) · Last modified: abril de 2014 (más de 12 meses; sigue vigente)
  14. F14 Set up MX records for Google Workspace (ayuda de Google Workspace) · Last modified: October 9, 2026
  15. F15 RFC 9989 · Domain-based Message Authentication, Reporting, and Conformance (DMARC) · Last modified: mayo de 2026 (reemplaza al RFC 7489)
  16. F16 Dedicated Email Sending Domains Overview & Setup · Last modified: April 17, 2026
  17. F17 Prevent Domain Connection Conflicts in Highlevel · Last modified: September 28, 2026
  18. F18 How to Set Up Root Domain/Subdomain for Funnels/Websites · Last modified: October 7, 2026
  19. F19 How to setup and configure a new domain or subdomain for GoHighLevel (growthable, fuente secundaria) · Last modified: 2023-01-28 (más de 12 meses)
  20. F20 How to Set Up a Whitelabel Domain for the Desktop Web App · Last modified: August 14, 2026
  21. F21 Branding System-Generated Links (API Domain) · Last modified: 2025-05-22 (más de 12 meses; HighLevel lo sigue enlazando)
  22. F22 Google Admin Toolbox · Last modified: no published date (checked on October 12, 2026)
  23. F23 ICANN Lookup · Last modified: no published date (checked on October 12, 2026)
  24. F24 ICANN Update: Launching RDAP; Sunsetting WHOIS · Last modified: 2025-01-27 (más de 12 meses)
  25. F25 Transfer Policy (ICANN) · Last modified: política vigente desde el 2016-12-01 (más de 12 meses)
  26. F26 Registrant Benefits and Responsibilities (ICANN) · Last modified: 2013 (más de 12 meses; sigue vigente)
  27. F27 Registering Domains Through Third Parties Safely (Dynadot, fuente secundaria) · Last modified: May 22, 2026
  28. F28 Registrar Non-Response (ICANN) · Last modified: 2014 (más de 12 meses; sigue vigente)
  29. F29 EPP Status Codes: clientTransferProhibited (ICANN) · Last modified: 2014 (más de 12 meses; sigue vigente)
  30. F30 Cloudflare Registrar (página del producto) · Last modified: sin fecha publicada (© 2026; consultada el 2026-10-12)
  31. F31 Register a new domain (Cloudflare Registrar Docs) · Last modified: April 24, 2026
  32. F32 Cloudflare Registrar FAQ · Last modified: August 3, 2026
  33. F33 Do You Have a Domain Name? Here's What You Need to Know (Part 5) (blog de ICANN) · Last modified: 2018-12-07 (más de 12 meses; sigue vigente)
  34. F34 Expired Registration Recovery Policy: what registrants should know (ICANN) · Last modified: 2018-12-07 (más de 12 meses; sigue vigente)
  35. F35 HighLevel · Terms of Service (sección 1, «Domain Names») · Last modified: Last Updated June 2026
  36. F36 How to Purchase Domain Step by Step · Last modified: October 8, 2026
  37. F37 LC Domain: Multiple Year Domain Purchase · Last modified: 2025-07-09 (más de 12 meses)
  38. F38 How to Enable and Rebill Domain Purchase? · Last modified: 2025-05-30 (más de 12 meses)
  39. F39 Transfer a Domain Out of HighLevel · Last modified: September 4, 2026
  40. F40 Verisign Reports First Quarter 2026 Results (Business Wire) · Last modified: April 23, 2026
  41. F41 About Cloudflare Registrar (Cloudflare Docs) · Last modified: April 24, 2026
  42. F42 .com en Cloudflare (domainoffer.net, fuente secundaria) · Last modified: precios actualizados el 11 y 12-oct-2026
  43. F43 .com en GoDaddy (domainoffer.net, fuente secundaria) · Last modified: precios actualizados el 11 y 12-oct-2026
  44. F44 .mx domain registration (Namecheap) · Last modified: consultada el 2026-10-12
  45. F45 .com.mx en Namecheap (domainoffer.net, fuente secundaria) · Last modified: precios del 12-oct-2026
  46. F46 .mx en Cloudflare (domainoffer.net, fuente secundaria) · Last modified: precios del 12-oct-2026
  47. F47 About .mx domains (ayuda de GoDaddy) · Last modified: no published date (checked on October 12, 2026)
  48. F48 Who can register .CO domains? (registro .CO) · Last modified: 2025-10-02 (algo más de 12 meses)
  49. F49 .co en Cloudflare (domainoffer.net, fuente secundaria) · Last modified: precios del 12-oct-2026
  50. F50 Dominios .es (Tu espacio europeo, administracion.gob.es) · Last modified: April 14, 2026
  51. F51 .es (domainoffer.net, fuente secundaria) · Last modified: precios del 12-oct-2026
  52. F52 Cloud Domains FAQ (Google Cloud) · Last modified: October 9, 2026
  53. F53 RFC 8659 · DNS Certification Authority Authorization (CAA) Resource Record · Last modified: noviembre de 2019 (más de 12 meses; sigue vigente)
  54. F54 Domain Transfer-out to Cloudflare · Last modified: October 8, 2026
  55. F55 Troubleshoot TXT records (ayuda de Google Workspace) · Last modified: October 7, 2026
  56. F56 How to add a domain and verify DNS records · Last modified: June 30, 2026