Help
Guides and troubleshooting. Expand a section for details.
How long do free-slot links last?
Free-slot previews created by a third party who is not the site owner (such as a hosting provider or agency) must be given to the end customer (for example, in the migration ticket). Free-slot links offered for commercial use are intended as an acquisition channel for paying customers. Links used only internally must be created as paid-slot links on a paid plan, regardless of traffic.
Within a rolling 30-day window per destination (hostname and origin IP), free-slot lifetime follows recent preview clicks:
- Up to 100 clicks: 1 week
- Above 100 clicks: 1 day
- Above 1,000 clicks: 1 hour
- Above 10,000 clicks: 1 minute
When a free-slot preview expires, you can renew it for free. Paid-slot links can be deleted to free a slot.
Paid-slot links use your plan slots and may include an optional custom expiration. You can convert a free-slot link to a paid-slot link from the dashboard when your plan includes paid slots, or buy a one-time extension. Guest trial links on the home page follow the same click-based lifetime rules. See Pricing and GET /system for integration fields.
What are paid slots?
Paid plans include a fixed number of paid slots. Each active paid-slot link uses one slot until you delete it or it reaches an optional end date you set. Deleting a paid-slot link frees the slot for a new link.
This is separate from Spaces, which are optional groupings with default routing—not slot counters. See Pricing for plan limits.
What are Spaces?
Spaces may be used to tag links (like Gmail labels) and to store default IP and HTTP/HTTPS port combinations. If you work with two or more servers, create one Space per environment with the correct defaults.
When adding a link, select the Space and leave IP/port blank—the link inherits the Space routing. Updating a Space’s routing applies to all links in that Space that rely on those defaults.
How SkipDNS works
Each request to a preview URL is forwarded to the server at the IP you configured (or to the IP the domain resolves to if you did not set one). Responses are rewritten so references to the real site hostname use the preview address instead, so pages, forms, and assets load through the proxy.
SkipDNS does not write proxied page content to disk. Operational data is limited to access logs (see Access logs). The consent page explains preview behavior on first visit to each alias.
Missing images or broken layout
References to the main site and www are rewritten to your preview alias.
Other subdomains are proxied through SkipDNS but forwarded to whatever IP public DNS returns—not necessarily the IP on the link form.
Missing images often mean a subdomain still points at old or offline hosting, or the origin blocks hotlinking from unknown referrers (your preview subdomain looks like a third-party site to the asset server).
If you are validating a migration, ask the destination host to check subdomain routing, PHP version, and hotlink rules.
On the link form, wildcard / multisite chooses whether only the apex and
www use the routing settings you configure there (other subdomains follow normal DNS), or every subdomain does.
Preview not loading over HTTPS (blank page or errors)
If the origin has no SSL certificate for the site yet, browsers may show a blank page when the preview uses HTTPS. Installing any certificate on the origin (even self-signed or for another name) usually fixes that.
Alternatively, enable Flexible SSL on the link (HTTPS port same as HTTP, often 80). SkipDNS terminates HTTPS on the preview and speaks HTTP to the origin. Internal links may still break or loop depending on the app—see below.
Apache (.htaccess) — add at the top of public_html/.htaccess:
SetEnvIf X-SkipDNS-Proto https HTTPS=on
SetEnvIf X-SkipDNS-Proto https SERVER_PORT=443
SkipDNS sends X-SkipDNS-Proto (and X-Forwarded-Proto) so the app knows the visitor used HTTPS on the preview URL.
PHP (e.g. WordPress) — in wp-config.php after the opening tag:
$_SERVER['HTTPS'] = 'on';
$_SERVER['SERVER_PORT'] = '443';
WordPress often needs only the first line. Adding both is safe for other CMSes that read the port.
Hosting providers can apply Apache rules globally—see Hosting providers.
I cannot receive the activation e-mail
Check your spam or junk folder and wait a few minutes—delivery can be delayed. Make sure you signed up with the correct address (typos are common).
If nothing arrives, try another e-mail address or contact us and we can help complete activation.
Automation and pre-filled URLs
REST API v2 is included on every plan—see Developers.
To pre-fill the link creation form, open a URL with the server IP and destination in the path (replace the placeholders in the examples below).
A hostname alone defaults to HTTPS; include http:// or a full URL in the destination segment when you need an explicit protocol or path.
For IPv6, colons in the address can confuse some clients—use square brackets around the IP when needed (both forms work).
https://skipdns.link/203.0.113.10/example.com
https://skipdns.link/2001:db8::1/example.com
https://skipdns.link/[2001:db8::1]/example.com
https://skipdns.link/203.0.113.10/https://example.com/blog
https://skipdns.link/203.0.113.10/http://legacy.example/old-site
For cPanel end customers, use the free cPanel plugin.
Hosting providers: server-wide Flexible SSL
SkipDNS discourages Flexible SSL—use it only as a last resort when a preview cannot load over HTTPS any other way. Current cPanel releases typically install a self-signed SSL certificate on new accounts by default, which is enough for HTTPS previews without Flexible SSL in most cases.
If you still need server-wide support—for example legacy servers without auto SSL, or apps that break unless Apache sees HTTPS—add the following to global Apache includes or your vhost template so customers do not have to edit each .htaccess:
SetEnvIf X-Forwarded-Proto https HTTPS=on
SetEnvIf X-Forwarded-Proto https SERVER_PORT=443
SkipDNS sends X-Forwarded-Proto and X-SkipDNS-Proto; prefer the forwarded-proto form when you can so the same rules also cover Cloudflare Flexible SSL, load balancers, and other reverse proxies.
Per-account troubleshooting (including .htaccess and app config) is described in
Help → HTTPS and blank pages.
cPanel plugin documentation · API for bulk or custom integrations
What access logs do you keep?
We retain standard access log fields: URL requested, timestamp, user agent, visitor IP, bytes transferred, HTTP status, and referrer when present. This is similar to what origin web servers typically log.
Forwarded requests include the visitor IP in headers; many origins log SkipDNS’s IP instead, which can add a layer of separation (not guaranteed).
See also Terms.
cPanel plugin
Install the SkipDNS cPanel plugin so customers create preview links from cPanel—free-slot defaults, paid slots, Flexible SSL, wildcard, API tokens, and updates are documented here:
How do custom domains work?
A custom domain must be a registrable apex (top-level) hostname such as example.com or example.co.uk. Subdomains like links.example.com are not accepted.
The domain must use Cloudflare DNS—this is required, with no alternative.
Set it up from the Domains page in your dashboard: add the domain and provide a Cloudflare API token with at least these permissions:
SkipDNS then creates DNS records for the domain and its wildcard, turns off selected Cloudflare zone settings that rewrite HTML/JS during migration previews, adds a cache bypass rule, and adds a security header rule.
Need more? Contact