Domain Setup (Optional)

Do You Need a Custom Domain?

No, and not at first. New organizations are provisioned with a working example decoy on the WebDecoy shared domain (*.d.webdecoy.com) as part of signup. You can create as many additional decoys as you want on the shared domain without configuring anything in DNS.

A custom domain is a branding upgrade, not a requirement. Add one when you want decoys served from your own hostname rather than <random>.d.webdecoy.com.

Shared Domain vs Custom Domain

	Shared domain (default)	Custom domain (optional)
Setup	None (works the moment you sign up)	DNS record + SSL provisioning (~15-60 min)
Decoy URL example	`abc12345.d.webdecoy.com/admin-login`	`cdn.yoursite.com/admin-login`
SSL	Wildcard cert managed by WebDecoy	Let’s Encrypt cert provisioned per domain
Best for	Trying out the product, internal testing, decoys hosted on third-party sites	Production deployments where decoys live under your brand

You can mix the two (some decoys on the shared domain, others on a custom domain) within the same organization.

Adding a Custom Domain

This three-step process configures DNS, verifies ownership, and provisions SSL.

Why Add a Custom Domain?

Benefit	Description
Brand consistency	Decoys appear as part of your real infrastructure
Phishing resistance	Attackers can’t pattern-match the shared hostname
SSL Included	Automatic HTTPS via Let’s Encrypt

Step 1: Enter Your Domain

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

What to Enter

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

Good Domain Name Examples

Domain	Why It Works
`cdn.yoursite.com`	Looks like a content delivery endpoint
`assets.yoursite.com`	Appears to serve static files
`api2.yoursite.com`	Suggests a backup API server
`secure.yoursite.com`	Implies security-related functionality

What to Avoid

Domain	Problem
`honeypot.yoursite.com`	Obviously a trap
`decoy.yoursite.com`	Reveals intent
`test.yoursite.com`	May already be in use

Skip Option

If you’re not ready to set up a domain, you don’t have to. Your shared-domain decoys keep working. You can come back here from Settings → Domains at any point.

Step 2: Configure DNS

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

A Record Configuration

You’ll see instructions like:

Field	Value
Type	A
Name	Your subdomain (e.g., `cdn`)
Value	The IP address displayed in WebDecoy
TTL	Auto (or 3600)

Adding the Record

Log into your DNS provider (Cloudflare, Route53, GoDaddy, etc.)
Navigate to DNS management for your domain
Create a new A record with the values shown
Save your changes

Provider-Specific Examples

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

Important Notes

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

Verifying DNS

Once you’ve added the record:

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

Check propagation manually:

dig cdn.yoursite.com A

Or use online tools like whatsmydns.net.

Step 3: SSL Certificate

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

What Happens

Automatic initiation - SSL provisioning starts immediately after DNS verification
HTTP-01 challenge - Let’s Encrypt validates domain ownership
Certificate issued - Usually takes 30-60 seconds
Domain ready - Your domain is now configured with HTTPS

SSL Status Indicators

Status	Meaning
Spinner	Certificate provisioning in progress
Green checkmark	Certificate issued successfully
Warning icon	Certificate issuance failed

If SSL Fails

If certificate provisioning fails:

Check error message - The error will indicate what went wrong
Click “Retry SSL” - Try provisioning again
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)

After Domain Setup

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

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

Next Steps

With your domain configured, you’re ready to:

Create Decoy Links - Build honeypot links on your domain
Set Up Detection Scripts - Add client-side detection
View Detections - Monitor incoming threats

Adding More Domains Later

You can add additional domains at any time:

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

See the Custom Domains guide for detailed domain management instructions.

Troubleshooting

DNS Verification Fails

Issue	Solution
“A record not found”	Wait a few minutes for DNS propagation
Wrong IP address	Double-check the IP matches what WebDecoy shows
Still failing	Check your DNS provider’s dashboard to confirm the record exists

SSL Certificate Fails

Issue	Solution
Timeout	Wait a moment and click “Retry SSL”
Validation failed	Ensure DNS is pointing correctly, Cloudflare proxy is off
Rate limited	Wait an hour before retrying

Need Help?

If you’re stuck during onboarding:

Click the Support link in the footer
Email [email protected]
Check the Troubleshooting guide