# FAQ ## General

1. What is Sol.site?

Sol.site is a experimental feature from SNS (Solana Name Service) that gives every .sol domain holder the an instant Web2 website address. **How it works:** * Buy `alice.sol` → automatically get `alice.sol.site` * No browser extensions needed * Compatible with all devices and browsers By default, `yourname.sol.site` displays a ready-made profile page. You can customize it to point to any hosting provider. You can also configure email using MX records, allowing you to receive mail at a custom address like `owner@yourname.sol.site`.

2. What can Sol.site be used for?

* **Personal brand:** portfolio, link hub, contact page * **Project site:** updates, docs, community access * **Business:** affordable web presence with Web3-native identity * **Email:** receive mail at `owner@yourname.sol.site`—your Web3 domain and Web2 contact in one

3. Does Sol.site cost extra?

**No.** It's included free with every .sol domain.

4. Which .sol domains are eligible for Sol.site?

Most .sol domains are eligible automatically. Restrictions apply to: * **Ineligible domains:** Listed domains, subdomains, and sub-registrars * **Characters:** Letters, numbers, and hyphens only—no emojis, special characters, or non-Latin scripts * **High-risk names:** Certain names (e.g., major brands) are blocked to prevent impersonation

5. How is this different from traditional web2 domains?

| Traditional Domains | .sol + sol.site | | ------------------------------------- | --------------------------- | | Recurring yearly fees (\~$10–20/year) | One-time fee | | No crypto functionality | Doubles as a wallet address | | Separate identity from Web3 | Web3 + Web2 in one |

6. I'm not technical. Can I still use it?

**Absolutely.** You get a ready-to-use profile page immediately after purchase. Just share your `yourname.sol.site` link—no setup required. Want to customize it later? We have step-by-step guides [here](https://docs.sns.id/collection/sns-v2/sol.site/website-configuration).

## Technical

1. What hosting providers can I use with Sol.site?

Any hosting provider that supports custom domains. This includes platforms like Vercel, Netlify, GitHub Pages, AWS, as well as self-hosted solutions like a VPS or IPFS. If your provider supports adding a custom domain via CNAME or A record, it works with sol.site.

2. How long does it take for Sol.site changes to propagate?

DNS changes typically take anywhere from a few minutes to 24 hours to propagate globally. Your site may resolve in some regions before others during this period.

3. What DNS record types are supported?

* **CNAME** * **A** * **AAAA** * **MX** * **TXT**

4. Can I set up email with my Sol.site domain?

Yes, Sol.site supports MX records, so you can use email providers like Google Workspace, Zoho, or ProtonMail. Simply configure the required MX and TXT (SPF/DKIM/DMARC) records as specified by your email provider.

5. Can I use SSL/HTTPS with my Sol.site domain?

SSL support depends on your hosting provider. Most modern platforms like Vercel, Netlify, and GitHub Pages automatically provision SSL certificates when you add a custom domain. If you're self-hosting, you can use services like Let's Encrypt to generate a free certificate.

6. Can I use my Sol.site domain with a CDN?

You can point your sol.site domain to a CDN by setting the appropriate CNAME record. However, CDN features that require full DNS delegation may not be supported.

## Security

1. How is my Sol.site isolated from other Sol.sites?

Every `yourname.sol.site` is treated as its own independent domain by browsers and other web services—just like any `.com` or `.co.uk`. This is made possible by Sol.site's inclusion in the [Public Suffix List (PSL)](https://publicsuffix.org/), a shared registry used by browsers to determine domain boundaries. This means other sol.site users cannot access your cookies, session data, or other browser-stored information. Sol.site was added to the PSL in Jan 2026. However, it may take time for browsers, hosting platforms, and other third-party software to update their local PSL data—until then, some services may not yet recognize Sol.site as a public suffix.

2. What is the Public Suffix List and why does it matter?

The PSL is a registry maintained by Mozilla that browsers and other software use to determine where one domain ends and another begins. Without it, `alice.sol.site` and `bob.sol.site` could potentially share cookies and session data. Being on the PSL ensures each Sol.site user is treated as a fully independent domain.

3. Should I use cookie-based sessions on Sol.site?

This is not recommended. While PSL inclusion provides isolation in modern browsers, outdated browsers or misconfigured clients may not respect PSL boundaries, potentially exposing session data across Sol.site users. Consider using token-based authentication (e.g., JWTs via headers) as a safer alternative.

4. Why won't my hosting provider verify my Sol.site domain?

* Some hosting platforms maintain their own copy of the PSL. If they haven't updated recently, they may reject `yourname.sol.site` during domain verification. This is not a sol.site issue — please contact your hosting provider and ask them to update their PSL data.

5. Are there other shared-domain risks I should know about?

Because Sol.site is on the PSL, modern software treats each `yourname.sol.site` the same as any standalone domain. Some edge cases may arise with software that hasn't updated their PSL yet: * Outdated browsers * Hosting/CDN platforms with stale PSL data * Legacy email clients mishandling SPF/DKIM on newer public suffixes These issues resolve as third-party software updates their PSL.

6. What happens when a .sol domain is transferred?

Once a .sol domain is transferred, its existing DNS records are marked as stale and will stop being served. Due to DNS caching, the previous site may still be accessible for up to 24 hours in some regions. For security reasons, the new owner must wait 48 hours after acquiring the domain before configuring their own Sol.site records.

## Troubleshooting

1. Why can't I configure Sol.site after acquiring a .sol domain?

For security reasons, there is a 48-hour waiting period after acquiring a domain before you can configure Sol.site records. This applies to new registrations, domain sales, and transfers.

2. Why isn't my Sol.site loading after I set up my DNS records?

DNS changes can take up to 24 hours to propagate. If your site still isn't loading after that, double-check that your on-chain records are correctly configured and that your hosting provider has your Sol.site domain added as a custom domain.

3.Why is my hosting platform asking me to verify Sol.site ownership?

Some hosting platforms may not yet recognize Sol.site as a public suffix. Since Sol.site is listed on the PSL, your `yourname.sol.site` should be treated as a standalone domain—no root domain verification needed. If your platform hasn't updated their PSL data, reach out to their support team and ask them to update. This is a third-party issue, not a Sol.site limitation.

4. Why is my Sol.site showing old or incorrect content?

This is usually a DNS caching issue. Try clearing your browser cache or using a different network. If the problem persists after 24 hours, verify your on-chain records are up to date.

5. Why isn't my SSL certificate working?

SSL certificates are provisioned by your hosting provider, not Sol.site. Make sure your hosting provider has successfully issued a certificate for your Sol.site domain. Some providers require DNS verification—check their documentation for specific steps.

6. Why isn't email working with my Sol.site domain?

Verify that your MX and TXT (SPF/DKIM/DMARC) records are correctly set on-chain. Also confirm that your email provider has finished verifying your domain—some providers can take up to 48 hours.