Domain Parking Terms

Effective 2026-11-05 · Version 2026-11-05

These Domain Parking Terms (“Parking Terms”) apply when you use domain parking, the part of the Service that monetizes domains you own but do not use for a website. They add to our Terms of Service and are part of the Agreement. Words defined in the Terms of Service have the same meaning here. If these Parking Terms conflict with the Terms of Service, these Parking Terms win for domain parking. You accept them when you tick the box on your parking access request, or when you accept a new version in the dashboard.

1. Definitions

• Parking: the domain parking part of the Service.
• Portfolio: a placement of the type “Parked domains” that groups your Parked Domains. Each Portfolio has one pair of nameservers, an optional list of countries and an optional fallback page.
• Parked Domain: a domain you add to a Portfolio. A Parked Domain is a Property under the Terms of Service.
• Visitor: a person, or anything else, that requests a Parked Domain.
• Fallback page: the https page you choose for a Portfolio or a Parked Domain, which Visitors are sent to when we do not send them to an Ad; if you have not chosen one, or it is not cleared for use (section 5.4), our own neutral page that says “This domain is parked”.

2. Access

2.1 Parking is available only to accounts we approve. You ask for access with the request form on the Domain parking page of the dashboard, and you accept these Parking Terms in the same step. We aim to answer within five business days, by email. We may ask for more information, and we may refuse a request at our discretion; if we do, we tell you the reason and you may send a new request.

2.2 One approval covers all of your Portfolios. While your request is under review you may create Portfolios and add domains, but they do not go live until we approve your account.

2.3 There is no fee to use Parking. When we approve your account we set your parking revenue share (section 8) and tell you the percentage in the approval email. It is separate from your revenue share for other Ads, and section 9.1 of the Terms of Service applies to it.

2.4 We may revoke your parking access at any time, including for a breach of the Agreement, a complaint, Invalid Traffic, or a risk to us, our advertising partners or Visitors. We tell you the reason by email. A revoked account cannot send a new request; only we can reinstate it, and we may set a new parking revenue share when we do. Section 9 explains what happens to your domains.

3. Your domains

3.1 You confirm that you own every domain you add, or are authorized by its owner to park it, that you will keep its registration current, and that neither the domain name nor its use with Parking infringes anyone’s trademark or other rights or breaks any law, registry or registrar policy.

3.2 You may not add a domain that copies or imitates a brand, trademark, person, government body or organization you do not own or represent, including misspellings of them (“typosquatting”). Our checks hold domains that look like a well-known brand for review before they can go live. A domain that passes our checks is not cleared by us, and you remain responsible for it.

3.3 Only whole registrable domains can be parked, not subdomains. Do not add a domain that a website, email or other service you need runs on: Parking replaces what the domain shows and, with nameservers (section 4.2), its email.

3.4 We may refuse, hold or suspend any domain at our discretion. We never become the owner or registrant of your domains, and Parking does not transfer any rights in them to us.

3.5 Control of the domain’s DNS decides who parks it. If another dlserve account proves control of a domain parked in your Portfolio, for example after you sold it, the domain moves to that account and stops earning for you. A domain we never see pointed to us within 14 days of being added (not counting time while your access request is under review) expires, and you can add it again.

4. DNS and what changes when you point a domain to us

4.1 You connect a domain in one of two ways, shown in the dashboard: by setting its nameservers to the pair we give you for the Portfolio, or by adding the CNAME records we give you at your own DNS host. Making these changes at your registrar or DNS host, correctly and in time, is your responsibility. Do not switch a domain before your access is approved: until then it stays offline.

4.2 Nameservers. While a domain uses our nameservers, we answer all DNS for it, and only with the records Parking needs. Before you switch, turn off DNSSEC at your registrar (remove the DS record), turn off URL forwarding and remove any other parking provider’s nameservers. Email for the domain stops working: we publish records that say the domain sends and receives no email (a null MX record, an SPF record of “-all” and a DMARC policy of “reject”). Subdomains and other records you had before stop working.

4.3 CNAME records. You keep your own DNS host, email and other records. You must keep the _acme-challenge records for as long as the domain is parked, and if your DNS host can proxy traffic (for example Cloudflare), the records that send traffic to us must be set to DNS only.

4.4 Certificates. We obtain and renew TLS certificates for each Parked Domain from Let’s Encrypt or another public certificate authority. Certificate authorities publish the domain names they certify in public Certificate Transparency logs.

4.5 Checks. We check every live domain’s DNS daily. If a check fails, we email you what to fix. If the next daily check also fails, the domain leaves Parking and stops earning, and you must fix its records and add it again.

4.6 You can point a domain away from us, or remove it from your Portfolio, at any time. Once you remove it, or our checks find that it no longer points to us (section 4.5), we stop serving it and delete its certificate.

5. How a visit works

5.1 When a Visitor opens a Parked Domain, our servers either send the Visitor’s browser straight to one Ad (a redirect), with no page in between, or send it to your Fallback page. The Visitor does not see a page from us unless it is our neutral page. We ask search engines not to crawl Parked Domains.

5.2 To request the Ad, our servers ask our advertising partners for an Ad on the Visitor’s behalf, with the information in section 10.2. The Visitor’s own browser then follows the redirect, so any click the Ad records comes from the Visitor’s browser, not from our servers.

5.3 Ad matching. We send keywords and a topic with each Ad request so the Ad fits the domain. We suggest them from the domain name, and you can change them in the dashboard. We may change how ad matching works, and test it by sending some Ad requests without keywords or a topic.

5.4 Fallback pages. A Fallback page must be an https address on a website you are entitled to send visitors to, and it must comply with section 4 of the Terms of Service. We check every fallback website with Google’s Web Risk service when it is first saved and then daily, so its address is sent to Google. We use a fallback website only while that check passes and we have not blocked it. A block or a failed check applies to every account that uses the same website, and Visitors then see our neutral page instead.

5.5 We do not guarantee that any visit is sent to an Ad, or any rate, price or amount of revenue. Section 8.2 of the Terms of Service applies.

6. Visits we do not send to Ads

6.1 To protect advertisers, we send a visit to the Fallback page, without requesting an Ad, when, for example:

• it does not look like a person opening the page: an empty or known crawler or bot browser identifier; a request from a frame, an embedded request, a prefetch or a preview;
• it comes from network addresses that crawlers and AI agents publish as their own, from Tor exit nodes, or from data-center and hosting networks, except published privacy relays (such as iCloud Private Relay);
• it comes from a country outside the Portfolio’s country list, if you set one;
• it goes over our limits: currently one Ad per Visitor per domain each hour, plus limits on visits per minute for each domain and each Portfolio;
• the Portfolio, the domain or Parking is paused (section 9), or our servers cannot confirm they have current settings.

6.2 We may add, change or remove these filters and limits at any time without notice. We do not report to you which visits were filtered or why.

6.3 Visits sent to the Fallback page earn nothing. Our advertising partners may also apply their own filtering, and Ads they decline or clicks they discard earn nothing.

7. Traffic quality

7.1 Section 7 of the Terms of Service (Invalid Traffic) applies to Parked Domains in full. In particular, you must not:

• request a Parked Domain, or have it requested, by bots, scripts or any automated means;
• open Parked Domains in frames, pop-ups, pop-unders or hidden windows, or redirect visitors to them without their knowledge;
• request Parked Domains in a way that does not follow the redirect to the Ad; or
• send paid, incentivized or redirected traffic to Parked Domains, unless you described that source in your access request or we agreed to it in writing.

7.2 Automatic pauses. When we confirm revenue (section 8), we compare the visits we redirected to Ads with the clicks our advertising partners counted for them. A report day on which a Portfolio had at least a minimum number of redirects (currently 500) and clicks were counted for fewer than a minimum share of them (currently half) is a low day. After two low days in a row (currently), we pause the whole Portfolio for 7 days. During the pause every visit goes to the Fallback page and earns nothing. We may change these thresholds, and we may end a pause early.

8. Revenue and payment

8.1 Estimated and confirmed revenue. When we redirect a visit to an Ad, we record the price our advertising partner quoted for it. This is estimated revenue, shown in your reports as Estimated. Revenue becomes Confirmed when our advertising partner reports what it will pay us for the domain for that day, usually within two days. Confirmed revenue replaces the estimate in your reports and can be lower or higher.

8.2 How we confirm a day. Our advertising partners report by day in their own time zone. We split each report day’s revenue for a domain across the two UTC days it covers, in proportion to our estimates for each part, so that the parts add up exactly to the reported amount. A Parked Domain that a report covering its Portfolio does not include earns zero for that day. If our advertising partner never reports a day, we may confirm it at zero.

8.3 What we pay. Your parking payout for a calendar month (UTC) is your parking revenue share of the confirmed revenue of your Parked Domains for that month. Estimated revenue is never paid. The parking payout is added to your monthly payout under section 9 of the Terms of Service. It is outside any minimum guarantee: parking revenue never counts toward a guarantee, and parking visits never count toward its base.

8.4 Held payouts. While any day of a month with parking activity on your account is not confirmed, your whole payout for that month, including revenue from your other Properties, waits and cannot be approved. Because the last day of each month is confirmed only after the next month starts, this normally adds a day or two. Once every day is confirmed, the payout is recalculated and goes through approval and payment as usual.

8.5 Adjustments. Sections 7.3, 9.2 and 9.5 to 9.7 of the Terms of Service apply to parking revenue. In particular, we may reduce, withhold or reverse parking revenue for Invalid Traffic, or where our advertising partners deduct, reverse or withhold payment for it, including after we have paid you.

9. Pauses, suspension and ending Parking

9.1 Pauses. We may pause Parking for one domain, a Portfolio, a region or everyone, at any time and without notice, for example for the reasons in section 7.2, while we investigate a complaint, or to protect the Service. During a pause the domain stays connected and visits go to the Fallback page, but earn nothing.

9.2 Suspension. We may suspend a Parked Domain at our discretion, for example after a complaint, an abuse report or a trademark claim. We delete a suspended domain’s certificate; if it uses our nameservers, we keep answering its DNS but it no longer leads to a website. It shows no Ads and earns nothing until we release it.

9.3 Revocation. If we revoke your parking access, every one of your Parked Domains is suspended as section 9.2 describes.

9.4 When Parking ends. Your domains stay yours. To use a domain elsewhere, change its nameservers at your registrar, or remove the records you added for us; we cannot do this for you. We pay confirmed revenue earned before a suspension, a revocation or the end of the Agreement in the normal payment cycle, subject to sections 7 and 9 of the Terms of Service.

10. Visitor information

10.1 You do not install any code for Parking. Our servers receive each request for a Parked Domain directly, and we decide how the information is used.

10.2 For each visit we receive the Visitor’s IP address, browser user agent and language, and the address requested. To request an Ad we send our advertising partners the Visitor’s IP address, user agent and language, the domain’s address, a reference to the domain, and the keywords and topic (section 5.3). When the Visitor’s browser follows the redirect, it connects to our advertising partners’ servers through web addresses we control, so they receive the Visitor’s IP address and browser details again.

10.3 We record each visit with its time, domain, outcome and estimated revenue, the country and region we work out from the IP address on our own servers, the browser and operating system, the network operator’s number, and a keyed hash of the Visitor’s network. We do not record the IP address or the user agent themselves. We keep these records for 30 days; daily totals per domain and country, which identify no Visitor, are kept without a fixed end date. To apply the limits in section 6.1 we keep a keyed hash of the IP address and user agent for the length of the limit, currently one hour. Backups of our databases are kept for up to 63 days. We set no cookies on Parked Domains, and our neutral page loads nothing from third parties.

10.4 Your reports show visits, redirects, revenue and revenue per thousand visits for each domain by day. We do not give you information about individual Visitors.

11. Information you give us

11.1 We keep the answers in your access request, and the record of which version of these Parking Terms you accepted, when and by whom, for as long as your account exists and afterwards as section 7 of our Privacy Policy allows for account records.

11.2 The optional report screenshot you upload with your access request is stored privately, without its file metadata, and only our review staff can see it. We delete it 180 days after we decide your request. A screenshot uploaded but never sent with a request is deleted after 24 hours.

12. Complaints and takedown

12.1 Report abuse, a trademark claim or any other complaint about a Parked Domain to hello@dlserve.ai, with the domain and the reason. We review each report and may suspend the domain at once while we do.

12.2 You will answer our questions about a complaint promptly and cooperate in resolving it. We may tell the person who complained that the domain was suspended, without naming you.

13. Indemnity

Section 15 of the Terms of Service applies to Parking. It also covers claims arising out of or relating to your domain names, including claims of trademark infringement, cybersquatting or typosquatting, your Fallback pages, the traffic you send to Parked Domains, and your breach of these Parking Terms.

14. Changes to these Parking Terms

14.1 We may change these Parking Terms. Each version carries a version and an effective date on this page. When we publish a new version, we email you and show it on the Domain parking page of the dashboard.

14.2 You must accept each new version in the dashboard. Until you do, you cannot create Portfolios or add domains. Your live domains keep earning for 30 days from the new version’s effective date. After that, your Portfolios are paused (section 9.1) until you accept; accepting ends that pause at once.

14.3 Until you accept a new version, the version you accepted before keeps applying to you. Section 17.1 of the Terms of Service does not apply to changes to these Parking Terms.

15. Attribution

This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com.

16. Contact

Questions about these Parking Terms: hello@dlserve.ai.