ShieldSignup

Providers/DuckDuckGo Email Protection

Relay / alias
email_relay

DuckDuckGo Email Protection

DuckDuckGo Email Protection issues @duck.com aliases that forward to a private address.

Duck.com aliases are usually privacy-motivated. Treat email_relay as a soft signal unless your policy blocks all relays.

Example domains

Public domains commonly associated with DuckDuckGo Email Protection. ShieldSignup coverage is broader (marketing: 94,000+ disposable domains) — this page lists examples only, not every domain the provider may use.

  • duck.com

Block with ShieldSignup

Call POST /v1/assess with the signup email. For known domains of this type, expect reason code email_relay and signals.email.relay_domain: true.

curl -sS -X POST https://www.shieldsignup.com/v1/assess \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{"email":"user@duck.com","ip":"203.0.113.10"}'

Read the temporary email blocking guide →

Related providers