Skip to content

Domain Setup

After creating your organization, WebDecoy guides you through setting up your first custom domain. This three-step process ensures your domain is properly configured with DNS and SSL before you start deploying decoys.

Custom domains are the foundation of effective deception:

BenefitDescription
AuthenticityDecoys appear as part of your real infrastructure
Immediate ProtectionStart collecting detections right away
SSL IncludedAutomatic HTTPS via Let’s Encrypt

The first step is to specify which domain you want to use for your decoys.

  • Enter a subdomain you control (e.g., cdn.yourcompany.com)
  • The subdomain should look legitimate to attackers
  • You’ll need access to your DNS provider to complete setup
DomainWhy It Works
cdn.yoursite.comLooks like a content delivery endpoint
assets.yoursite.comAppears to serve static files
api2.yoursite.comSuggests a backup API server
secure.yoursite.comImplies security-related functionality
DomainProblem
honeypot.yoursite.comObviously a trap
decoy.yoursite.comReveals intent
test.yoursite.comMay already be in use

If you’re not ready to set up a domain, you can click “Skip to Dashboard” and configure domains later from Settings → Domains.


After entering your domain, WebDecoy displays the DNS record you need to create.

You’ll see instructions like:

FieldValue
TypeA
NameYour subdomain (e.g., cdn)
ValueThe IP address displayed in WebDecoy
TTLAuto (or 3600)
  1. Log into your DNS provider (Cloudflare, Route53, GoDaddy, etc.)
  2. Navigate to DNS management for your domain
  3. Create a new A record with the values shown
  4. Save your changes

Cloudflare:

Type: A
Name: cdn
IPv4 address: <IP from WebDecoy>
Proxy status: DNS only (grey cloud) ← Important!

Route53:

Record name: cdn.yoursite.com
Record type: A
Value: <IP from WebDecoy>
TTL: 300

GoDaddy:

Type: A
Host: cdn
Points to: <IP from WebDecoy>
TTL: 1 Hour
  • Cloudflare users: Disable the proxy (use grey cloud, not orange)
  • DNS propagation: Usually takes just a few minutes, but can take up to an hour
  • Copy buttons: Click the values in WebDecoy to copy them to your clipboard

Once you’ve added the record:

  1. Click “Verify DNS” in the onboarding flow
  2. WebDecoy checks if your A record is correctly configured
  3. If verification fails, wait a few minutes and try again

Check propagation manually:

Terminal window
dig cdn.yoursite.com A

Or use online tools like whatsmydns.net.


After DNS verification, WebDecoy automatically provisions an SSL certificate from Let’s Encrypt.

  1. Automatic initiation - SSL provisioning starts immediately after DNS verification
  2. HTTP-01 challenge - Let’s Encrypt validates domain ownership
  3. Certificate issued - Usually takes 30-60 seconds
  4. Domain ready - Your domain is now configured with HTTPS
StatusMeaning
SpinnerCertificate provisioning in progress
Green checkmarkCertificate issued successfully
Warning iconCertificate issuance failed

If certificate provisioning fails:

  1. Check error message - The error will indicate what went wrong
  2. Click “Retry SSL” - Try provisioning again
  3. Or skip to Dashboard - You can retry from Settings → Domains later

Common issues:

  • DNS not fully propagated yet
  • Cloudflare proxy is enabled (should be disabled)
  • Rate limiting from Let’s Encrypt (wait an hour)

Once your domain shows “Domain Ready!”, you’re all set:

  1. Click “Go to Dashboard” to continue
  2. Your domain appears in Settings → Domains
  3. You can now create decoys using this domain

With your domain configured, you’re ready to:


You can add additional domains at any time:

  1. Go to Settings → Domains in the sidebar
  2. Click “Add Domain”
  3. Follow the same DNS verification and SSL setup process

See the Custom Domains guide for detailed domain management instructions.


IssueSolution
”A record not found”Wait a few minutes for DNS propagation
Wrong IP addressDouble-check the IP matches what WebDecoy shows
Still failingCheck your DNS provider’s dashboard to confirm the record exists
IssueSolution
TimeoutWait a moment and click “Retry SSL”
Validation failedEnsure DNS is pointing correctly, Cloudflare proxy is off
Rate limitedWait an hour before retrying

If you’re stuck during onboarding: