Help

How to transfer Web2 domains from one Freename account to another

Freename — Wed, 08 Apr 2026 16:23:35 GMT

If you own a Web2 domain such as Example.com registered with Freename and would like to transfer it to another Freename account, the process is simple and straightforward.

Here’s a step-by-step guide to help you complete the transfer smoothly.

Transfer a Web2 Domain to Another Freename Account

Transferring your domain to another Freename user only takes a few minutes.

Just follow the steps below:

1. Log in to Your Freename Account

Start by signing in to your Freename account and navigating to your Portfolio.

2. Open Domain Management

Locate the domain you wish to transfer and click on Manage.

3. Initiate the Transfer

Select Transfer, then click Unlock Transfer to enable the process.

4. Enter the Recipient’s Email

Type in the recipient’s Freename account email address carefully to ensure accuracy.

5. Confirm the Transfer

Review the details and confirm the transfer request.

What Happens Next?

Once the transfer has been initiated, it usually takes anywhere from a few minutes to a few hours to complete.

And that’s it! With just a few clicks, your Web2 domain can be securely transferred to another Freename account.

If you encounter any issues, you can always reach out to Freename’s support team for assistance.

FAQ

Can I transfer my Web2 domain to another Freename account?

Yes, if you own a Web2 domain (such as Example.com) registered with Freename, you can easily transfer it to another Freename account by following the transfer steps in your portfolio.
How long does it take to transfer a Web2 domain within Freename?

The transfer process only takes from a few minutes to a few hours.
Where do I start the domain transfer process?

You need to log in to your Freename account, go to your Portfolio, select the domain, and click Manage to access the transfer option.
Why do I need to unlock the domain before transferring?

Unlocking the transfer is a security step that allows the domain to be moved to another account. Without unlocking it, the transfer cannot proceed.
What information is required to transfer the domain?

You must enter the recipient’s Freename account email address accurately. If the email address is incorrect, the domain may be sent to the wrong recipient or the transfer may be delayed or fail.
What should I do if the transfer does not go through?

If you encounter any issues during the transfer process, you can contact Freename’s support team for assistance.

How long does it take to mint my domain?

Freename — Wed, 08 Apr 2026 13:28:06 GMT

Minting generally take a few hours based on blockchain network and Traffic. Sometimes due to heavy traffic it may take up to 72 hours.

Factors Influencing Minting Time

Several key factors determine the duration of the NFT minting process:

Blockchain Network: Different blockchains have varying transaction speeds.
Network Congestion (Traffic): When a blockchain network is experiencing high demand (many people trying to mint or transact simultaneously), transaction times increase significantly.
Smart Contract Complexity: More complex smart contracts might require slightly longer processing times, though this is usually a minor factor compared to network traffic.
Transaction Confirmation Status: The process is complete only once the transaction has been confirmed and included in a block on the blockchain, which can take time depending on block intervals and confirmation requirements.

FAQ

How long does it take to mint an NFT?

Minting generally takes a few hours, depending on the blockchain network and current traffic. However, during periods of heavy congestion, it may take up to 72 hours for the transaction to be completed and confirmed.
Why does network traffic affect minting time?

When many users are minting or making transactions at the same time, the blockchain network becomes congested. This increases processing times because validators prioritize transactions based on fees and network demand.
Which blockchain mints NFTs faster?

Different blockchains have different speeds. For example, Polygon is generally faster.
How do gas or transaction fees impact minting speed?

Gas fees (such as those on Polygon and similar networks) determine transaction priority. Paying a higher fee increases the likelihood that validators will process your transaction more quickly.
Does smart contract complexity affect minting time?

Yes, but only slightly. More complex smart contracts may require additional processing, though this is usually a minor factor compared to network congestion and transaction fees.
When is the minting process officially complete?

Minting is complete only after the transaction has been confirmed and added to a block on the blockchain. Confirmation times depend on the network’s block intervals and required confirmations.
Are there any minting fees?

Currently, we cover the minting fees.

Where can I sell my domains?

Freename — Wed, 08 Apr 2026 13:06:54 GMT

Selling your domain names can be a smart way to monetize your digital assets, whether they are traditional Web2 domains or blockchain-based Web3 domains. Freename offers powerful tools and marketplaces to help you sell domains efficiently and transparently.

This article explains the main places you can sell your domains, how they work, and what makes each option unique.

1. Freename Aftermarket: Primary Marketplace

The Freename Aftermarket is the go-to marketplace for buying and selling domains, both Web2 and Web3. It is a universal domain marketplace designed to give sellers exposure to a large audience of buyers and investors.

How It Works

List your domain directly in the Aftermarket with a fixed price.
Buyers browse a wide variety of domains and complete the purchase instantly.
The platform supports domains registered in both Web2 (e.g., .com, .net) and Web3 (e.g., .metaverse, .satoshi).
You can see more details on how to sell in this article.
How to Sell Any Domain on Freename Aftermarket

Key Features

Web2 + Web3 in One Place: You can sell traditional DNS domains and decentralized Web3 domains side by side.
Escrow-Assisted Transactions: The marketplace handles payment escrow and domain transfer, providing security for both buyer and seller.
AI-Powered Search & Categories: Buyers can filter domains by category, trend, or value to find the right matches faster.
Zero Commission (Limited Time): In certain promotional periods, Freename offers 0% trading commission, maximizing your returns.

Who It’s Best For

Sellers who want broad exposure
Investors and flippers
Owners of both Web2 and Web3 domains

2. Domora: Fractionalized Domain Ownership (Only for Web2 Domains)

Domora is a newer platform that enables a different selling model: fractional ownership of premium domains. Instead of selling a domain outright, you can sell shares (units) of the domain to multiple buyers.

How Domora Works

You verify and transfer your domain into the Domora platform.
The domain is fractionalized into tradable units on-chain.
Buyers invest in units, giving them a share of ownership without requiring full domain control.
You can see more details on how to fractionalize your domain in this video.
How to: Fractionalize Your Domain on Domora

Key Benefits

Unlock Liquidity: Instead of waiting for one buyer who can afford the entire domain, you can sell parts of it to many buyers.
Broader Investor Base: Fractional ownership opens premium domain value to users with smaller budgets.
On-Chain Transparency: All ownership and transactions are recorded on blockchain for auditability.

Who It’s Best For

Owners of premium domains
Sellers looking for liquidity without full transfer
Community-oriented domain projects

Which Option Should I Choose?

If you want to sell your domain completely → Use Freename Aftermarket
If you own a premium Web2 domain and want to fractionalize it → Use Domora
If you are selling Web3 domains → Use Freename Aftermarket

Notes

Domains listed on the Aftermarket are available for direct purchase.
Domora is designed specifically for premium Web2 domains with fractional ownership.
Availability of certain features may depend on the domain type.

If you have any questions about where or how to sell your domain, please contact our support team. Our team will be happy to assist you.

FAQ

Can I sell both Web2 and Web3 domains on Freename?

Yes. Freename allows you to sell both Web2 and Web3 domains through the Freename Aftermarket.
What is the difference between Aftermarket and Domora?

The Freename Aftermarket is designed for direct domain sales to a single buyer.
Domora allows premium Web2 domains to be fractionalized and sold in shares to multiple investors.
Is Domora available for Web3 domains?

Domora is currently designed for premium Web2 domains with fractional ownership. Web3 domains can be sold directly through the Freename Aftermarket.
Do I need to transfer my domain before fractionalizing it on Domora?

Yes. The domain must be transferred to the Domora platform before it can be fractionalized.

Additionally, domains must be renewed for at least three years before being fractionalized to ensure stability throughout their lifecycle on the platform.
How do I set the price of my domain in aftermarket?

When listing on the Aftermarket, you can define a fixed price for your domain. Pricing can be based on market trends, keyword value, brand potential, and recent comparable sales.
Set a fair price: Research similar recent sales before setting your price.
What happens after my domain is sold?

Once the purchase is completed, the transfer process is initiated and managed through the platform to ensure a secure transaction between buyer and seller.
Can I remove my domain from sale at any time?

Yes. You can manage your listings and update or remove them directly from your account dashboard.

How to point a domain to Zoho Mail

Freename — Wed, 08 Apr 2026 12:50:32 GMT

When you're ready to use Zoho Mail with your custom domain, the first step is to point your domain's DNS records to Zoho Mail’s servers. This ensures that your emails will be routed through Zoho's platform. Here's a step-by-step guide to help you set up your domain to work with Zoho Mail.

Step 1: Add MX Records

To point your domain's email to Zoho Mail, you'll need to configure your domain’s MX (Mail Exchange) records in the DNS manager. Here are the entries you need to add:

First Entry (MX Type):

Name: @
Priority: 10
Destination: mx.core.locaweb.com.brmx.zoho.com (or Default)

Second Entry (MX Type):

Name: @
Priority: 20
Destination: mx2.zoho.com
TTL: 14400 (or Default)

Third Entry (MX Type):

Name: @
Priority: 50
Destination: mx3.zoho.com
TTL: 14400 (or Default)

Once these records are added to your domain’s DNS settings, your emails will start being routed through Zoho’s mail servers.

Step 2: Authenticate Your Domain Using a TXT Record

Zoho Mail requires you to verify ownership of your domain by adding a TXT record to your domain’s DNS settings. Follow these steps to authenticate your domain:

1. Copy the Unique TXT Code

Log in to the Zoho Mail Admin Console.
Navigate to the Domains section on the left panel.
If you've already added your domain, click on it from the list. If not, click + Add to add a new domain.
In the domain verification section, choose the option "Add a TXT record to DNS" from the dropdown list.
Copy the generated TXT value from the Zoho Mail Admin Console.

2. Add the TXT Record to Your Domain’s DNS Settings

Log in to your Freename account
Go to Freename's website and log in to your account using your credentials.
Navigate to the DNS Manager

From your dashboard, go to the Portfolio section.
Select Domains from the left-hand menu.
Click on the domain name that you want to update.

Access the DNS Zone

In the domain management page, find and click on DNS Records.
This will take you to your DNS Zone where you can manage all the DNS settings for your domain.

Add a TXT Record

Click on the Add Record button.
From the dropdown menu, choose TXT as the record type.
In the Name field, enter @ to indicate the root domain.
In the Value field, paste the unique TXT value you copied from the Zoho Mail Admin Console.
Set the TTL (Time to Live) to 14400 (or leave it as Default).

Save the Record
Once you've entered the TXT record details, click on Save to add it to your DNS settings.

3. Verify the TXT Record

Return to the Zoho Mail Admin Console, and in the Domain section, click on Verify.
Zoho will check if the TXT record has been successfully added and will verify the domain ownership.

Once verified, your domain will be successfully linked with Zoho Mail!

FAQ

How long does it take for MX and TXT records to propagate?
DNS changes typically take anywhere from a few minutes to 72 hours to propagate globally. Make sure to give it enough time before verifying the changes in Zoho Mail.
What do I do if the TXT record verification fails?
If verification fails, double-check that the TXT record was added correctly to your DNS settings. Ensure there are no extra spaces or typos in the record.
Can I use Zoho Mail with multiple domains?
Yes, Zoho Mail supports multiple domains. You can add additional domains through the Zoho Mail Admin Console and configure the DNS records for each one separately.
Do I need to remove old MX records from my DNS?
Yes, if you're switching from another email provider, it's a good practice to remove any old MX records from your DNS settings to ensure email routing is directed solely to Zoho Mail.
Can I point my domain to Zoho Mail without using a TXT record for verification?
No, Zoho Mail requires domain verification to ensure you own the domain. The TXT record is the method used to verify ownership.

How to point a domain to Shopify

Freename — Wed, 08 Apr 2026 10:58:26 GMT

Connecting your domain to Shopify allows you to use your custom domain for your online store instead of the default yourstore.myshopify.com address.

This guide explains how to properly configure your DNS records inside Freename so your domain connects correctly to Shopify.

1. Prerequisites

Before you begin, make sure you have:

An active Shopify store
Access to your Freename domain panel
Your domain added inside Shopify

⚠️ Important:
DNS changes are not instant. Propagation can take up to 48–72 hours globally.

2. Required DNS Records for Shopify

To connect your domain to Shopify, you need to add the following DNS records:

2.1 A Record (Root Domain)

This connects your main domain (example.com) to Shopify.

Type	Name	Value	TTL
A	@	23.227.38.65	1 hour

Explanation:

@ represents the root domain (example.com).
23.227.38.65 is Shopify’s server IP.

2.2 CNAME Record (www Subdomain)

This connects the www version of your domain.

Type	Name	Value	TTL
CNAME	www	shops.myshopify.com	1 hour

Explanation:

This ensures www.example.com properly points to Shopify.

3. Add DNS Records in Freename

Log in to your Freename Panel
Navigate to:
Portfolio → Domains → Manage → DNS
Add the A record:

Type: A
Name: @
Value: 23.227.38.65
TTL: 1 hour

Add the CNAME record:

Type: CNAME
Name: www
Value: shops.myshopify.com
TTL: 1 hour

Save changes.

⚠️ If you have any existing A or CNAME records that conflict, remove them before adding Shopify’s records.

4. Verify Your Domain in Shopify (TXT Record)

In some cases, Shopify requires domain verification using a TXT record.

4.1 Retrieve the Verification Value

Open a new tab.
Log in to your Shopify Admin.
Go to:
Settings → Domains
Click the domain you’re verifying.
Locate the New value shown.
Click the copy icon.

4.2 Add the TXT Record in Freename

Return to your Freename DNS panel and add:

Type	Name	Value	TTL
TXT	@	(value copied from Shopify)	1 hour

Save the record.

5. Complete Domain Connection in Shopify

After DNS propagation:

Go back to Shopify Admin → Settings → Domains
Click Verify connection
Once verified, you can set the domain as Primary

6. DNS Propagation & Troubleshooting

Because DNS updates must propagate worldwide, you may experience delays.

To check propagation:

Visit:
https://dnschecker.org
Select:

A record (for root domain)
CNAME record (for www)

Enter your domain and search.

You should see:

A record pointing to 23.227.38.65
CNAME pointing to shops.myshopify.com

If propagation exceeds 72 hours:

Confirm records were added correctly
Ensure no conflicting A/CNAME records exist
Confirm you are editing the correct domain

FAQ

1. How long does it take for my domain to connect to Shopify?

DNS propagation typically takes anywhere from a few minutes up to 48–72 hours. While many connections activate within a few hours, global DNS servers need time to update.

2. My domain isn’t loading my Shopify store yet. What could be wrong?

The most common reason is DNS propagation delay. However, you should also verify:

The A record is set to 23.227.38.65
The CNAME record for www is set to shops.myshopify.com
There are no conflicting A or CNAME records
You are editing the correct domain in Freename

3. How can I check if my DNS records have propagated?

You can use a public DNS tool:

Go to https://dnschecker.org
Select:

A record (for your root domain)
CNAME record (for www)

Enter your domain and click search.

You should see:

A record → 23.227.38.65
CNAME → shops.myshopify.com

If results vary by location, propagation is still in progress.

4. Do I need to delete old DNS records before adding Shopify’s records?

Yes. If other A or CNAME records exist for the same host (@ or www), they may conflict with Shopify’s configuration. Remove conflicting records before saving the new ones.

5. Why is Shopify asking me to verify my domain with a TXT record?

Shopify sometimes requires domain ownership verification before activating the connection.

To complete this:

Go to Shopify Admin → Settings → Domains
Click your domain
Copy the New value
Add it as a TXT record in Freename
Wait for propagation
Click Verify connection in Shopify

6. What should I do if it still doesn’t work after 48 hours?

If more than 48 hours have passed:

Double-check the A and CNAME values
Confirm TTL is set to 1 hour (or default)
Make sure you saved the DNS changes
Verify that the correct domain is being edited
Confirm the domain is properly added inside Shopify

If everything is configured correctly but the issue persists, you can contact us via Live Chat or e-mail at support@freename.com

How to point your domain to a VPS hosting

Freename — Wed, 08 Apr 2026 10:18:43 GMT

Pointing a Web2 domain to a VPS (Virtual Private Server) is a common way to publish a website, application, or service under your own domain. Depending on your provider, this is done either by pointing DNS records to a server IP or by following the provider’s required DNS setup (for example, specific CNAME records or nameserver changes).

This guide explains how DNS resolution works, which records you need, and how to point your Web2 domain using Freename’s DNS panel.

1. Prerequisites

Before you start, make sure you have:

A Web2 domain registered with Freename (e.g. yourdomain.com)
A VPS with a public IP address
- IPv4 (e.g. 203.0.113.10)
- Optional IPv6 (e.g. 2001:db8::1)
Access to Freename’s DNS panel
A web server installed on your VPS (Apache, Nginx, etc.)

No additional tools are required.

2. How Domain → VPS Resolution Works

When a user visits your domain:

The browser queries DNS for your domain
DNS returns the IP address of your VPS
The browser connects directly to your server
Your web server responds with the website or application

This mapping is done using A records (IPv4) and optionally AAAA records (IPv6).

3. Identify Your VPS IP Address

From your VPS provider dashboard or server console, locate:

Public IPv4 address (most common)
Optional: IPv6 address

Example:

IPv4: 203.0.113.10

IPv6: 2001:db8::1

You will use these values in the DNS configuration.

4. Add an A Record in Freename (IPv4)

4.1 Access the DNS Panel

2 Navigate to:

Portfolio → Domains → Manage → DNS

3 Select the domain you want to point to your VPS

4.2 Create the A Record

Add a new DNS record with the following values:

Host / Name: @ (root domain)
Type: A
Value: Your VPS IPv4 address (e.g. 203.0.113.10)
TTL: 300 or default

Save the record.

This points:

yourdomain.com → VPS IP

5. (Optional) Add an AAAA Record (IPv6)

If your VPS supports IPv6, you can also add an AAAA record.

Host / Name: @
Type: AAAA
Value: Your VPS IPv6 address
TTL: 300 or default

This allows IPv6-capable clients to connect directly.

6. Point the WWW Subdomain to Your VPS

Most websites should also respond to www.yourdomain.com.

Option 1: Add a CNAME Record (Recommended)

Host / Name: www
Type: CNAME
Value: yourdomain.com
TTL: 300 or default

This ensures www always follows the root domain.

Option 2: Add a Separate A Record

Alternatively, you can point www directly to the IP:

Host / Name: www
Type: A
Value: Your VPS IPv4 address

Both approaches work, but CNAME is preferred for simplicity.

7. Configure Your Web Server (VPS Side)

DNS only routes traffic — your VPS must be configured to accept it.

On your VPS:

Configure your web server (Apache / Nginx) with:
- ServerName yourdomain.com
- ServerAlias www.yourdomain.com
Ensure port 80 (HTTP) and 443 (HTTPS) are open
Restart the web server after configuration

Without this step, DNS will resolve correctly but the website may not load.

8. DNS Propagation & Verification

DNS changes are not instant.

8.1 Check Propagation

You can verify DNS propagation using:

https://dnschecker.org/

Select A
Enter your domain
Confirm the VPS IP appears globally

Propagation usually takes minutes, but can take up to 72 hours.

9. SSL Certificate (Important)

After DNS is pointing to your VPS, you should install an SSL certificate.

Common options:

Let’s Encrypt (free)
Cloudflare (proxy-based)
Commercial SSL providers

Without SSL, browsers will show security warnings.

10. Common Issues & Troubleshooting

Website not loading

VPS firewall blocking ports 80/443
Web server not running
Virtual host misconfiguration

DNS not resolving

Wrong IP entered
DNS not saved
Propagation still in progress

WWW works but root doesn’t (or vice versa)

Missing A or CNAME record
Web server missing ServerAlias

FAQ

What DNS records do I need to point a Web2 domain to a VPS?
You need an A record to map your domain to the VPS IPv4 address, and optionally an AAAA record if you also want to support IPv6.
How do I point the root domain (yourdomain.com) to my VPS in Freename?
In Freename’s DNS panel, create an A record with Host/Name = @, Type = A, Value = your VPS IPv4, and TTL = 300 (or default), then save.
How should I configure the www subdomain (www.yourdomain.com)?
Recommended: add a CNAME with Host/Name = www pointing to yourdomain.com.
Alternative: add a separate A record for www pointing directly to your VPS IPv4.
Why can DNS be correct but the website still doesn’t load?
DNS only routes traffic. Your VPS must have a web server configured with ServerName yourdomain.com and ServerAlias www.yourdomain.com, and ports 80 (HTTP) and 443 (HTTPS) must be open. Then restart the web server.
How long does DNS propagation take and how can I verify it?
Propagation can take minutes but up to 72 hours. You can check it on dnschecker.org by selecting A, entering your domain, and confirming your VPS IP appears globally.

What are SPF, DKIM and DMARC Records?

Freename — Mon, 23 Feb 2026 15:56:03 GMT

Email authentication helps protect your domain from spam, phishing, and unauthorized senders. Three main systems work together to keep your emails legitimate: SPF, DKIM, and DMARC.

Together, they ensure that only approved servers can send email from your domain — and they help mail providers decide what to do when something looks suspicious.

1. What Are SPF, DKIM, and DMARC?

SPF (Sender Policy Framework)

SPF is a DNS record that lists which servers are allowed to send email from your domain.
You can think of SPF as a guest list — if a server is not on the list, it should not be sending messages as you.

Example SPF record:

v=spf1 ip4:192.0.2.0 include:examplesender.net -all

v=spf1 → says this is an SPF record
ip4:192.0.2.0 → an allowed sending IP
include:examplesender.net → also trust this provider
-all → block everything not listed

Without SPF, your emails may end up in spam, and attackers may more easily impersonate your domain.

DKIM (DomainKeys Identified Mail)

DKIM adds a digital signature to your emails.
Your outgoing server signs the message with a private key, and the receiving server checks it using a public key stored in your DNS.

In simple terms:

DKIM proves that the email really came from your domain
It also confirms that the message was not modified during delivery

A DKIM record is stored as a TXT record using a selector, like this:

bigemail._domainkey.example.com

TXT

v=DKIM1; p=PUBLICKEYGOESHERE

If the signature matches, the email passes DKIM.

DMARC (Domain-based Message Authentication, Reporting & Conformance)

DMARC tells email providers what to do when SPF or DKIM fail.

It acts as your policy:

Should failed messages be delivered anyway?
Should they be marked as spam?
Should they be rejected completely?

Example DMARC record:

_dmarc.example.com

TXT

v=DMARC1; p=quarantine; rua=mailto:reports@example.com

DMARC also allows you to receive reports about who is trying to use your domain.

Domains without DMARC are easier to spoof and more likely to have email delivery issues.

2. Why These Records Matter

If SPF, DKIM, and DMARC are not configured:

Your emails may go to spam, fail delivery, or get quarantined
Attackers can impersonate your domain more easily
Mail providers may distrust your domain

Correct configuration ensures:

Higher deliverability
Better protection against phishing
More control over how your domain is used

Even domains that do not send email should still publish a DMARC record to prevent abuse.

3. Simple Example of Each Record

SPF

v=spf1 include:_spf.google.com -all

DKIM

google._domainkey.example.com

TXT

v=DKIM1; p=PUBLICKEY

DMARC

v=DMARC1; p=reject; rua=mailto:you@example.com

FAQ

What is SPF, and what problem does it solve?

SPF (Sender Policy Framework) is a DNS record that specifies which mail servers are allowed to send email on behalf of your domain. It works like a permission list: if a server is not included in the SPF record, it should not be sending messages “as you.” When SPF is missing or incorrect, legitimate emails can be treated as suspicious and may end up in spam, and it becomes easier for attackers to impersonate your domain from unauthorized servers.
How does DKIM work, and what does it guarantee?

DKIM (DomainKeys Identified Mail) adds a digital signature to your outgoing emails. Your sending server signs each message using a private key, and the receiving server verifies that signature using a public key that you publish in DNS as a TXT record (often under a selector like bigemail._domainkey.example.com). If the signature checks out, DKIM passes. This demonstrates two key points: the email genuinely originated from your domain’s authorized sending system, and the message content was not altered during delivery.
What is DMARC, and what does it tell email providers to do?

DMARC (Domain-based Message Authentication, Reporting & Conformance) is a policy layer that instructs mail providers how to handle messages when SPF or DKIM fail. In other words, it tells providers whether suspicious messages should still be delivered, moved to spam/quarantine, or rejected completely. A DMARC record is published in DNS (commonly under _dmarc.example.com as a TXT record) and can include a policy such as p=quarantine or p=reject. This gives you more control over how your domain is used and how providers respond when something looks wrong.
Why do SPF, DKIM, and DMARC matter for deliverability and security?

These three systems work together to help mail providers determine whether email claiming to be from your domain is legitimate. Without them, providers may be more likely to distrust your domain, which can cause messages to be sent to spam, quarantined, or fail delivery. From a security perspective, missing authentication makes it easier for attackers to spoof your domain for phishing attempts. Correct configuration supports higher deliverability, better protection against phishing, and clearer control over what happens to suspicious messages.
If my domain doesn’t send email, do I still need anything?

Yes. Even if your domain is not used to send email, publishing a DMARC record is still recommended to reduce the risk of abuse. The article specifically notes that domains without DMARC are easier to spoof and more likely to have email delivery issues. Adding DMARC helps signal to mail providers how to treat unauthenticated mail that pretends to come from your domain, which improves protection against impersonation and misuse.

How to point a domain to Google Sites

Freename — Mon, 23 Feb 2026 15:24:38 GMT

This guide explains how to point a domain registered with Freename to a website created on Google Sites. By completing this setup, visitors will be able to access your Google Site using your custom domain.

Before you begin, make sure that:

Your website is already created and published on Google Sites.
You have access to your Freename account and DNS management.
You understand that DNS changes may take up to 72 hours to fully propagate.

Step 1 – Get the DNS Records from Google Sites

Open Google Sites.
You need to Configure your domain in the Google Sites platform.
Go to Settings → Custom domains.
Click Start setup and enter your domain name.
Google will provide one or more DNS records

Keep this information available, as you will need it in the next steps.

Step 2 – Access DNS Management in Freename

Log in to your Freename account.
Open your Portfolio → Domains → Select the domain you want to point to Google Sites and click Manage.
Access the DNS zone editor

.

Step 3 – Set Up A Records

Create the following A records in your domain’s DNS zone:

	Record 1	Record 2	Record 3	Record 4
Name	@	@	@	@
Content	216.239.38.21	216.239.36.21	216.239.34.21	216.239.32.21

To add, go to DNS record and click Add a record.

The result will look like this:

Make sure to delete any other A (@) records that may have been previously added so that only these four remain.

Step 4 – Set Up a CNAME Record

Delete all the current CNAME records (if any), and create a new CNAME with the following value:

Name: www
Content: ghs.googlehosted.com

It will look like this:

Once you do that, DNS propagation will start. This process can take up to 72 hours. During this time, it’s expected that your website won’t work, but give it some time, and it will get online soon.

Step 5 – Verify Your Domain

Once DNS propagation is over, verify your domain with Google. Go back to Google’s official guide and follow the steps in the section Verify ownership of your domain.

After successful verification, it might take a few hours for Google to recognize the changes and for your website to start working with the new domain.

NOTES:

The propagation of any record can take up to 72 hours to fully propagate, so after making the change, it is important to wait if your website is not working.
To check propagation, visit the website DnsChecker, enter your domain and the record you added, and check how it is going. If 72 hours have passed and you notice that propagation is "stuck," please contact our support team.

FAQ

Can I point a Freename Web2 domain to Google Sites?

Yes. You can point a Web2 domain registered with Freename to a website created on Google Sites so visitors can access your site using your custom domain.
What do I need before connecting my domain to Google Sites?

Your website must already be created and published on Google Sites, you must have access to your Freename account and DNS management, and you should be aware that DNS changes can take up to 72 hours to propagate.
Which DNS records are required to connect a domain to Google Sites?

You must add four A records for the root domain (@) with the IP addresses provided by Google, and one CNAME record for www pointing to ghs.googlehosted.com. Any existing A (@) or CNAME records should be removed before adding these.
Do I need to manage DNS through Google or Freename?

DNS management remains on Freename. You add and manage the required A and CNAME records directly in the Freename DNS zone editor.
Why do I need to verify my domain with Google Sites?

After DNS propagation is complete, domain verification is required so Google can confirm ownership and correctly associate your custom domain with your Google Site.
How long does it take for my Google Site to work with my domain?

DNS propagation can take up to 72 hours. After verification, it may take a few additional hours for Google to recognize the changes and for the website to become accessible.

Send or receive crypto with Web3 domain on Bitcoin.com wallet

Freename — Fri, 20 Feb 2026 17:26:03 GMT

Using a Web3 domain with Bitcoin.com Wallet makes sending and receiving crypto much simpler.

Instead of using a long and complicated wallet address like:

0xghhdb...

you can use a readable Web3 domain, such as:

YourName.YourTLD

Your Web3 domain is linked to your wallet address, and Bitcoin.com Wallet automatically resolves the domain to the correct address when sending funds. This removes the need to copy and paste long wallet strings and helps reduce mistakes.

This makes crypto transfers faster, easier, and more user-friendly, especially for people who are not comfortable checking long wallet addresses every time.

How to Receive Crypto with Your Web3 Domain on Bitcoin.com Wallet

To receive crypto using your Freename Web3 domain, follow these steps:

Register a Web3 domain with Freename
Mint the domain
Go to Web3 Domains → Manage → Records → Wallet Address
Add your wallet address (if it is not already connected)
Sign the transaction to confirm and save the record on-chain

Once your wallet address is set, you can simply share your domain (for example, YourName.YourTLD) with anyone who wants to send you crypto using Bitcoin.com Wallet.

How Sending Crypto Works in Bitcoin.com Wallet

When sending crypto through Bitcoin.com Wallet, the sender can enter your Web3 domain instead of your full wallet address.

Bitcoin.com Wallet resolves the domain to the wallet address stored in your domain records, and the funds are sent directly to your wallet.

This creates a much smoother experience because:

it is easier to read and share a domain name
it reduces copy/paste mistakes
it saves time when making repeated transactions

What Happens After the Sender Enters Your Domain?

Once the sender types your Freename domain into Bitcoin.com Wallet:

The wallet checks the domain records
It resolves the domain to your linked wallet address
The sender confirms the transaction
The crypto is sent directly to your wallet

No manual address copy/paste is needed, as long as your domain has been correctly configured with your wallet address.

FAQ

1. How does sending crypto with a Web3 domain work on Bitcoin.com Wallet?

On Bitcoin.com Wallet, the sender can type a Freename Web3 domain instead of a long wallet address. The wallet automatically resolves the domain to the correct address saved in the domain records, making the transaction faster and easier to complete.

2. How do I receive crypto using my Freename domain on Bitcoin.com Wallet?

First, register and mint your Freename Web3 domain. Then go to Manage → Records → Wallet Address, add your wallet address, and sign the transaction to confirm the record. After setup, you can share your domain name and receive crypto through Bitcoin.com Wallet.

3. What happens after someone enters my domain in Bitcoin.com Wallet?

Bitcoin.com Wallet reads the wallet address linked to your domain and uses it as the destination for the transaction. Once the sender confirms, the crypto is sent directly to your wallet, just like a normal transfer, but without entering the full address manually.

4. Where is Bitcoin.com Wallet supported?

For sending crypto to a Web3 domain on Bitcoin.com Wallet, users should install the Bitcoin.com Wallet mobile app on their device.

You can install the app on:

Android (Google Play): https://play.google.com/store/apps/details?id=com.bitcoin.mwallet
iOS (App Store): https://apps.apple.com/us/app/bitcoin-com-wallet-buy-sell/id1252903728

5. What should I do if my domain is not resolving?

If you have waited more than 24 hours and your domain is still not resolving in Bitcoin.com Wallet, make sure you completed the “Sign the transaction” step in your Freename account under your domain management settings. If the issue continues, please contact us at support@freename.com.

Web3 domains use cases and benefits

Freename — Fri, 20 Feb 2026 17:14:49 GMT

Freename Web3 domains represent a new way to own and use domain names on the decentralized internet. With Freename, your domain becomes a digital asset, permanent, and secure.

What are Web2 and Web3?

Web2 is the internet we use today, allowing people to freely share information, create and publish content, interact, and collaborate with other user-generated content. Web3 is the concept of the next version of the internet, one that is decentralized through blockchain technology.

What Are Web3 Domains?

Web3 domains are domain names recorded and stored on a blockchain instead of being managed solely through traditional DNS systems. Once you mint or register a Web3 domain on Freename, it becomes your digital asset, similar to an NFT, that you truly own without ongoing renewal fees.

Unlike Web2 domains that require annual renewals and remain subject to centralized oversight, Web3 domains are permanent and decentralized.

Key Benefits of Freename Web3 Domains

Full Ownership

Your domain is permanently recorded on the blockchain. You control it directly through your wallet.

No Renewal Fees

You pay once. There are no annual renewals or hidden costs.

Decentralized Digital Identity

Your domain becomes your identity on Web3, usable for websites, wallets, and communication.

Monetization Through Royalties

If you create your own TLD (such as .brand or .chain), you can earn royalties every time someone registers a domain under it.

Create Your Own Namespace

Freename allows you to mint your own top-level domains, something that is not possible in the traditional DNS system.

Blockchain Transparency

Ownership can be verified on-chain through Web3 Whois and blockchain explorers.

Web3 Email & Communication

Your domain can be used as a Web3 email address.

Web3 Domains vs Web2 Domains

Feature	Web2 Domains	Web3 Domains (Freename)
Ownership	Rented	Fully owned
Renewal fees	Annual	None
Control	Centralized	Decentralized
Identity	Limited	Wallet-based
Monetization	Not possible	Possible with Royalties
Digital asset	No	Yes

Real-World Use Cases

Personal and brand identity
Decentralized websites
Crypto payments using human-readable names
Web3 email and messaging

Why Choose Freename?

Freename bridges traditional internet infrastructure with Web3 innovation. As an ICANN-accredited registrar, it supports both Web2 and Web3 domains in a unified platform while offering advanced Web3 capabilities like decentralized identities, royalty systems, and domain tool integrations.

By combining blockchain storage with familiar DNS compatibility, Freename ensures its domains work both in decentralized environments and across modern internet tools.

This means you can manage:

Traditional Web2 domains
Web3 blockchain domains
Custom TLDs

All from a single platform.

Freename bridges the traditional internet and the decentralized web, giving users control over their digital identity and online presence.

Freename Web3 Tools and Services

Freename provides a complete Web3 ecosystem that allows you to use your domain far beyond a traditional website address. With Freename, your domain becomes a digital identity, a communication tool, and a gateway between Web3 and Web2.

Web3 Mail

Your Freename domain can be used as a Web3 email address.

Web3 Mail can be used for:

Secure communications
Wallet-linked identity
Simplified Web3 interactions

Browser Extension

Freename offers an official browser extension that allows you to access Web3 features directly from your browser.

With the extension, you can:

Automatically redirect Web3 domains to Web2 websites

The extension can be downloaded here:
https://freename.com/downloads

This allows you to browse Web3 domains as easily as traditional websites.

Freename DNS and Domain Resolution

Freename provides a full Web3 DNS platform.

Using Freename DNS, you can:

Resolve Web3 websites built with Duda or Pagy on Chrome, Mozilla Firefox, and other browsers.

This allows your Web3 domain to function as both a decentralized domain and a gateway to traditional websites.

Website Builder

Freename integrates Duda or Pagy, allowing you to build complete Web3 websites using a visual, user-friendly website builder

With this integration, you can:

Create decentralized websites
Connect your site directly to your Freename domain

No advanced technical knowledge is required.

Privacy and Security

Freename Web3 domains leverage blockchain technology to record domain ownership on-chain, providing transparency and verifiable ownership.

Key characteristics include:

Blockchain-based ownership records
Transparent and verifiable domain control
Reduced reliance on traditional intermediaries
Enhanced user control compared to conventional domain systems

Freename domains can also be used as crypto payment addresses, allowing others to send payments using a human-readable domain name instead of a long wallet address.

Notes

We always recommend having an active Freename account and a connected wallet to access and manage all Web3 features properly.
Web3 domain resolution depends on proper DNS configuration and browser support.

If you have any questions or need assistance, please contact our support team. Our team will be happy to help.

FAQ

What is a Freename Web3 domain?

A Freename Web3 domain is a domain name recorded on the blockchain. Once minted or registered, it becomes a digital asset you control via your wallet, built for Web3 identity and on-chain ownership.
Is a Freename Web3 domain an NFT?

It is similar to an NFT because it is a blockchain-based digital asset you can verify on-chain. The key point is that ownership is controlled by your wallet.
Do Freename Web3 domains require yearly renewals?

No. Freename Web3 domains are typically pay once, with no annual renewal fees, since ownership is recorded on-chain.
How do I manage ownership and control of my Web3 domain?

You manage it through your wallet. The connected wallet controls the domain, and ownership can be verified on-chain via Web3 Whois or blockchain explorers.
What can I use a Freename Web3 domain for?

You can use it for decentralized websites, crypto payments with a human-readable name, and more.
What tools does Freename provide for Web3 domains?

Freename offers Freename DNS, Freename Extension, Web3 Whois and Web3 Explorer.

Help

How to transfer Web2 domains from one Freename account to another

Transfer a Web2 Domain to Another Freename Account

What Happens Next?

FAQ

How long does it take to mint my domain?

Factors Influencing Minting Time

FAQ

Where can I sell my domains?

1. Freename Aftermarket: Primary Marketplace

How It Works

Key Features

Who It’s Best For

2. Domora: Fractionalized Domain Ownership (Only for Web2 Domains)

How Domora Works

Key Benefits

Who It’s Best For

Which Option Should I Choose?

Notes

FAQ

How to point a domain to Zoho Mail

Step 1: Add MX Records

Step 2: Authenticate Your Domain Using a TXT Record

1. Copy the Unique TXT Code

2. Add the TXT Record to Your Domain’s DNS Settings

3. Verify the TXT Record

FAQ

How to point a domain to Shopify

1. Prerequisites

2. Required DNS Records for Shopify

2.1 A Record (Root Domain)

2.2 CNAME Record (www Subdomain)

3. Add DNS Records in Freename

4. Verify Your Domain in Shopify (TXT Record)

4.1 Retrieve the Verification Value

4.2 Add the TXT Record in Freename

5. Complete Domain Connection in Shopify

6. DNS Propagation & Troubleshooting

FAQ

How to point your domain to a VPS hosting

1. Prerequisites

2. How Domain → VPS Resolution Works

3. Identify Your VPS IP Address

4. Add an A Record in Freename (IPv4)

4.1 Access the DNS Panel

4.2 Create the A Record

6. Point the WWW Subdomain to Your VPS

Option 1: Add a CNAME Record (Recommended)

Option 2: Add a Separate A Record

7. Configure Your Web Server (VPS Side)

8. DNS Propagation & Verification

8.1 Check Propagation

9. SSL Certificate (Important)

10. Common Issues & Troubleshooting

FAQ

What are SPF, DKIM and DMARC Records?

1. What Are SPF, DKIM, and DMARC?

SPF (Sender Policy Framework)

DKIM (DomainKeys Identified Mail)

DMARC (Domain-based Message Authentication, Reporting & Conformance)

2. Why These Records Matter

3. Simple Example of Each Record

SPF

DKIM

DMARC

FAQ

How to point a domain to Google Sites

Step 1 – Get the DNS Records from Google Sites

Step 2 – Access DNS Management in Freename

Step 3 – Set Up A Records

Step 4 – Set Up a CNAME Record

Delete all the current CNAME records (if any), and create a new CNAME with the following value:

Once you do that, DNS propagation will start. This process can take up to 72 hours. During this time, it’s expected that your website won’t work, but give it some time, and it will get online soon.

Step 5 – Verify Your Domain

FAQ

Can I point a Freename Web2 domain to Google Sites?

What do I need before connecting my domain to Google Sites?

Which DNS records are required to connect a domain to Google Sites?

Do I need to manage DNS through Google or Freename?

Send or receive crypto with Web3 domain on Bitcoin.com wallet