To get started, all you need is a few DNS entries:
example.com IN A 18.104.22.168 www.example.com IN A 22.214.171.124 dnsperch.example.com IN TXT "user:john;price:2500"
The username you picked when you signed up for DNSPerch.
- The price to display on the landing page.
askto leave the price unspecified.
noneif the domain is not for sale.
ISO 4217 currency code
specifying which currency the
price is in.
price:270000;currency:JPY will result in “¥270,000”.
Language(s) to use for the landing page,
all to enable all available languages.
If more than one language is given (separated by commas),
the one that best matches the user's browser settings will be used;
if none match then the first language in the list will be used.
Languages other than English are community translations provided by DNSPerch users. Contact us with corrections or for information on submitting translations for new languages.Currently supported languages:
Whether or not an SSL certificate should be obtained from Let’s Encrypt for the domain. If this is turned off, the domain will still be available via HTTPS, but a self-signed certificate will be used instead, causing the browser to display an error message. This does not enable settings such as HSTS, HPKP, or HTTP redirects, so it is safe to leave this enabled unless you have specific concerns about certificate issuance for your domain.
yes Advanced Plan
Display “Powered by DNSPerch" at the bottom of the landing page.
ga_id Advanced Plan
The property ID of the Google Analytics property to associate with this domain. If you don't know it, you can find the property ID with the GA Account Explorer. Using this setting will add the analytics.js tracking snippet to your landing page.
piwik_url Advanced Plan
piwik_idsite Advanced Plan
piwik_url is the base URL for your Piwik installation, such as
The beginning of the URL controls whether to use HTTP or HTTPS for your Piwik installation:
//- Connect to Piwik using the same protocol as the page was served with. Note: This requires the Piwik server to support both HTTP and HTTPS connections.
https://- Always connect to Piwik using HTTPS, even for visits to the HTTP landing page. Note: This requires the Piwik server to support HTTPS connections.
http://- Always connect to Piwik using unsecured HTTP. Warning: This will cause mixed content errors for most browsers, so visits to HTTPS landing pages will probably not be tracked. (Of course, this is not a problem if you have also set
letsencryptoff. However, we do not recommend doing this.)
piwik_idsite is the site ID of the website you want to track visits for.
To find the idSite for your website, see the Piwik FAQ entry
How do I find the website ID?
Using these settings will add the Piwik tracking code to your landing page.
Questions? Comments? Want to chat?
Send an email to firstname.lastname@example.org. We're here to help!