Domain policy

Domains registered through SKAVON are subject to the following, in addition to the general Terms of service.

Registry rules govern

Every domain is ultimately subject to the rules of its registry (the organization that operates that TLD, e.g. NIXI for .in, Verisign for .com) - not just SKAVON's own policies. Where a registry requires something SKAVON's general process doesn't (for example, NIXI's e-KYC requirement for .in registrations), that requirement applies and SKAVON will tell you about it during checkout rather than after.

Accurate registration information

You must provide accurate registrant contact information. Registries can suspend a domain over inaccurate WHOIS data - this is a registry action, not something SKAVON can override.

Renewal is your responsibility

SKAVON does not currently auto-renew domains. You are responsible for renewing before expiration. A domain that lapses may enter a registry-defined redemption period (with restore fees set by the registry, not SKAVON) or may become available for anyone to register, depending on the TLD.

Transfers

Transferring a domain to or from SKAVON follows standard registry transfer rules: an authorization code (EPP code) from the losing registrar, a transfer lock that must be disabled before initiating, and a waiting period defined by the registry, not SKAVON.

DNS and nameservers

You are responsible for the nameservers you point your domain at, and for the DNS records served there. SKAVON does not currently operate DNS hosting - see the Terms of service for detail.

WHOIS and privacy

Whether WHOIS privacy/redaction is available, and what it costs, depends on the TLD and the upstream registrar's support for it - SKAVON will show what's actually available for a given TLD rather than promising privacy protection universally.

Restricted and special TLDs

Some TLDs carry extra requirements (KYC documents, local presence requirements, restricted eligibility). SKAVON only offers a TLD for registration once it's confirmed available and priced through the upstream provider - it does not promise support for a TLD it can't actually fulfil.