ESC
Quick Actions
Open Dashboard Console
View Developer API
Platform Features
View Active TLDs & Pricing
Browse Premium Vault
Read the Documentation
Global Whois Lookup
About Us
Contact Support Team

Table of Contents

Official Documentation Hub

Welcome to the comprehensive guide for deploying, managing, and securing your global infrastructure using the Registry platform. Master everything from basic namespace provisioning to advanced Edge API integrations.

1.1 Platform Overview & Architecture

Registry is not merely a standard domain registrar; it operates as an advanced Global Edge Routing Protocol engineered for modern, high-performance applications. By provisioning a namespace through our platform, your infrastructure is instantaneously propagated across our massive global Anycast network.

This deep integration ensures that you benefit from single-digit millisecond latency, enterprise-grade Layer-7 Web Application Firewalls (WAF), and automated threat mitigation right out of the box.

Initialize Your Identity

1.2 Authentication & Two-Factor (2FA)

We strictly adhere to a Zero-Trust Security architecture. To ensure the absolute integrity of your account and infrastructure, Two-Factor Authentication (2FA) is highly recommended and may be enforced globally by network administrators.

Securing Your Identity Protocol:

  • Access the Console

    Authenticate via standard encrypted credentials. If global 2FA is active, an initial One-Time Password (OTP) will be dispatched to your email.

  • Navigate to Identity Settings

    From your primary dashboard, access the Identity Settings interface. Locate the "Mandatory Authentication Method" panel.

  • Link Authenticator Application

    Select the "Authenticator App" protocol. Scan the generated QR Code using Google Authenticator, Authy, or any standard TOTP application. Input the 6-digit cryptographic code to finalize the binding process.

Operational Note: You may revert to the default Secure Email OTP at any time. If you lose access to your hardware device, please open a support transmission.

1.3 WHOIS Matrix Verification

In strict compliance with international ICANN registry regulations, maintaining an accurate and verified WHOIS identity is mandatory. Our automated compliance systems continuously monitor profile integrity.

Failure to provide a valid Phone Number, Verified City, and Physical Address will trigger an automated deployment block. You will observe a critical red alert banner within your dashboard if your identity parameters are deemed incomplete.

To rectify this, navigate to the Identity Matrix, complete the "General Info" parameters, and execute the "Synchronize Identity" command.

1.4 Quota Management System

To maintain absolute network stability and prevent resource abuse, every verified identity is assigned a strictly monitored deployment quota. This dynamic value dictates the maximum aggregate of active namespaces you are authorized to maintain simultaneously.

Your current utilization metrics are continuously displayed on the real-time Quota Bar located in the left navigation panel of your Dashboard.

2.1 Claiming a Namespace (Deploy Zone)

Provisioning a new namespace and deploying it to the edge is streamlined into a seamless, automated process executing in mere seconds.

  • Search & Verify Availability

    Utilize the "Deploy New Namespace" query interface on your Dashboard. Input your desired nomenclature, select the appropriate Top-Level Domain (e.g., .com, .dev) from the dropdown matrix, and initiate the availability scan.

  • Execute Deployment Sequence

    If the namespace is available and unreserved, trigger the "Deploy Zone" command. The platform will initialize a deployment loader, automatically communicating with the global API to provision your zone on the edge.

2.2 Advanced DNS Manager & Bulk Operations

Establishing connections between your allocated namespace and your origin servers requires precise DNS record configurations.

Single Record Injection

Navigate to the Manage Zone interface for your specific domain. Within the "Advanced DNS Records" module, you can manually inject A, CNAME, TXT, or MX records. To target the root domain hierarchy, utilize the @ symbol in the Name parameter.

Bulk Import Engine (JSON/CSV)

For large-scale migrations, leverage the "Bulk Import" functionality. This initializes an overlay modal where you can paste raw DNS configurations. Our parsing engine automatically formats and dispatches the payload to the edge network.

// Authorized JSON Payload Structure[ {"type":"A", "name":"api", "content":"192.168.1.1"}, {"type":"CNAME", "name":"www", "content":"target.app"}, {"type":"TXT", "name":"@", "content":"v=spf1 mx ~all"} ]// Authorized CSV Payload Structure (Type, Name, Target)A, mail, 10.0.0.5 CNAME, portal, platform.provider.com

2.3 Nameserver Delegation Authority

By default, the platform leverages our deeply integrated Edge Proxy network to ensure maximum security and speed. However, for users requiring absolute external control over their zone files, we offer Custom Nameserver (NS) Delegation.

Critical System Override: Selecting "Custom External NS" within the Nameserver Routing tab will permanently lock your Advanced DNS Manager interface. All routing authority will be delegated to your external provider.

2.4 Edge Page Rules (URL Forwarding)

Implement highly efficient HTTP redirects directly at the edge layer without requiring a backend origin server or writing server-side code.

Navigate to the Routing Tab within your Zone Management console. Input your destination uniform resource locator (e.g., `https://github.com/your-repo`), and execute the "Activate Route" command. The system will instantly deploy a 301 Forwarding Page Rule via the API.

2.5 Edge Speed & Cache Control

Control the global caching nodes directly from your console to ensure visitors always see the most up-to-date iterations of your deployed applications.

  • Purge Entire Edge Cache

    Executing the "Purge Everything" command sends a destruction signal to all global edge nodes. This forces the network to fetch a fresh, un-cached version of your assets from your origin server.

  • Engage Development Mode

    If you are actively pushing rapid code deployments, engage "Development Mode". This temporarily bypasses all caching layers, allowing real-time visibility of changes.

3.1 DEFCON 1 Panic Mode (DDoS Mitigation)

Emergency Threat Neutralization

In the event of a catastrophic Layer-7 DDoS attack or a massive automated botnet swarm, the DEFCON 1 Panic Mode serves as your ultimate infrastructure kill-switch. Navigate to the Security Tab and trigger the ENGAGE PANIC MODE sequence.

This action instantly injects aggressive mitigation rules across your entire zone. All incoming traffic will be aggressively filtered through a computational challenge, completely neutralizing malicious automated scripts before they reach your origin.

3.2 Cryptographic DNSSEC Validation

Protect your incoming traffic from devastating DNS cache poisoning, unauthorized zone spoofing, and Man-In-The-Middle (MITM) redirection attacks by enabling Domain Name System Security Extensions (DNSSEC).

Toggling the "DNSSEC Status" switch within the Security console will instruct the edge network to apply cryptographic signatures to all your DNS records. Note that global resolver validation may take up to 24 hours.

3.3 SSL/TLS Encryption Configuration

Absolute control over the cryptographic handshake between the Edge Network and your Origin Server is vital for compliance and security:

  • Flexible Mode: Encrypts traffic solely between the client browser and the Edge. Recommended only if your origin server cannot support an SSL certificate.
  • Full Mode: Encrypts traffic end-to-end. Requires an SSL certificate on your origin server.
  • Full (Strict) Mode: The highest echelon of security. Mandates end-to-end encryption requiring a strictly valid, unexpired certificate natively signed by a trusted CA on your origin server.

3.4 Quantum Secret Vault (Burn-After-Reading)

Transmitting plaintext passwords, sensitive API keys, or root server credentials across standard communication channels is a critical security vulnerability. Our platform incorporates a Quantum Secret Vault designed specifically for secure data transmission to Network Administrators.

When generating a Support Ticket or submitting a reply, select the "Encrypt with Burn-After-Reading Protocol" checkbox. Once viewed, the system automatically purges the data from the underlying database.

4.1 Team RBAC (Role-Based Access Control) Setup

Securely delegate infrastructure management responsibilities without compromising your master account credentials.

Within the Team Tab of your Zone Manager, input the registered email address of your developer or agency partner to dispatch a secure access invitation.

Upon formal acceptance, they are granted scoped permissions allowing them to manipulate DNS records and routing configurations. Crucially, they are strictly prohibited from initiating zone deletions, ownership transfers, or altering team structures.

4.2 Cryptographic Domain Ownership Transfers

Execute secure, permanent namespace ownership handovers utilizing our dual-handshake protocol:

  1. Access the Transfer Tab within the specific Zone Management console.
  2. Input the exact verified email address of the target recipient and execute the "Initiate Transfer" command.
  3. The designated recipient must authenticate into their dashboard to review and formally accept the request.
  4. Critical Event: Upon target acceptance, the platform automatically purges all existing Team Members and irrevocably shifts the root ownership.

4.3 Automated Ledger & PDF Invoicing

Every successful namespace deployment, renewal sequence, or financial transaction automatically triggers our internal accounting engine.

The system generates compliant invoice records dynamically. Navigate to the Ledger & Invoices module within your Identity Matrix. From here, you can execute one-click downloads of high-fidelity PDF documents.

5.1 Telegram Bot CLI Integration

Monitor and command your infrastructure securely from your mobile device without authenticating through the standard web console.

Registry CLI
@RegistryCLI_bot
Open in Telegram
Initialization Process: Before executing commands, you must link your identity. Send the /login your_email@domain.com command to the bot to securely bind your Telegram profile to your account.
// --- Identity & Availability ---/profile - View quota and account status./check [domain] - Query registry availability and pricing.// --- Deployment & Ledger ---/domains - List all active and pending namespaces./deploy [domain] [type] [targ] - Provision zone from chat.// --- DNS & Routing Control ---/dns_list [domain] - View active advanced DNS records./dns_add [dom] [type] [name] [targ] - Add advanced DNS record./ns [dom] [type] [ns1] [ns2] - Delegate custom Nameservers.// --- Security & Performance ---/purge [domain] - Clear entire Edge Cache./panic [domain] [on/off] - Engage DEFCON 1 DDoS mitigation./delete [domain] - Permanently purge a zone.

5.2 Multi-Channel Webhook Routing

Break free from the limitations of standard email alerts. Integrate critical infrastructure notifications—such as domain expiration warnings, DNS mutation alerts, and support matrix updates—directly into your organization's daily communication workflows.

Navigate to the Channels & Webhooks module within your Identity Settings. Here you may define specific API endpoints and activate routing toggles to dispatch JSON payloads directly to Discord, Slack workspaces, or custom internal endpoints.

5.3 Developer REST API Integration

Treat your infrastructure as code. Our comprehensive RESTful API exposes total programmatic control over your zones, DNS configurations, and edge caching behaviors.

Initially, you must generate your unique cryptographic Master Token (Format: RPRO_...) from the "Developer REST API" sector within your Identity Settings. This token acts as your root key and must be included within the standard Authorization: Bearer HTTP header for all programmatic requests originating from your CI/CD pipelines.

Snippets
deploy.sh
cache_purge.py
deploy.sh
#!/bin/bash# Deploy a new zone via standard cURLcurl -X POST "https://api.registry.meetsakib.com/v1/zones" \ -H "Authorization: Bearer RPRO_YOUR_SECURE_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "subdomain": "api", "parent": "domain.com", "type": "A", "content": "192.168.1.1" }'
import requests url = "https://api.registry.meetsakib.com/v1/zones/cache/purge"headers = { "Authorization": "Bearer RPRO_YOUR_SECURE_TOKEN", "Content-Type": "application/json"} payload = { "zone_id": "1942", "purge_everything": True} response = requests.post(url, json=payload, headers=headers)print(response.json())