Cryptographic Proof

Domain Verification

Cryptographic domain proof in minutes. Industry-standard DNS TXT, HTTP file, or webmaster email verification - the same methods Google, AWS, and Microsoft use. Essential for vendor onboarding, partnership verification, and business transactions.

How It Works

Industry-standard domain control verification

Step 1

Create Verification

Call our API with the domain name. We generate a unique verification token and instructions.

Step 2

User Proves Ownership

Domain owner adds a DNS TXT record (manually or auto-created via registrar), hosts a file, or confirms via webmaster email.

Step 3

Proof Generated

We verify the record/file exists and return a cryptographic proof of domain control.

Auto-DNS Technology

Automatic DNS Provider Detection

We detect your DNS provider automatically from nameserver records. For supported providers, we can create the verification TXT record for you - no manual DNS editing required.

155+
DNS Providers Detected
59
With Auto-Create TXT

Supported Providers Include

cloudflare logo
Cloudflare
godaddy logo
GoDaddy
aws logo
AWS
google cloud logo
Google Cloud
azure logo
Azure
digitalocean logo
DigitalOcean
namecheap logo
Namecheap
vercel logo
Vercel
netlify logo
Netlify
ovh logo
OVH
hetzner logo
Hetzner
porkbun logo
Porkbun

+ 140 more providers including regional registrars and managed DNS services

API Integration

Integrate domain verification seamlessly

1. Create Verification Request

curl -X POST https://api.proof.holdings/api/v1/verifications \
  -H "Authorization: Bearer pk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "domain",
    "channel": "dns",
    "identifier": "example.com"
  }'

2. Verify the Proof Token

# Trigger verification check after setup
curl -X POST https://api.proof.holdings/api/v1/verifications/VERIFICATION_ID/verify \
  -H "Authorization: Bearer pk_live_YOUR_API_KEY"

Response Example

{
  "id": "507f1f77bcf86cd799439011",
  "status": "verified",
  "verified_at": "2026-03-15T10:55:00Z",
  "verified_data": {
    "record_found": true,
    "record_value": "proof-verify=A7B3X9"
  },
  "proof": {
    "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
    "expires_at": "2026-04-14T10:55:00Z"
  }
}