1. Help Center
  2. Tests/Campaigns

Configure a Custom Domain or CNAME

You can use the Hook Security platform with domains that you own or control. You will need access to the domain's DNS records. 

Below are links to "How To" for configuring DNS settings in some common registrars.

Go Daddy

Network Solutions

Wild West Domains



If you're setting up a subdomain (such as www.somecompany.co.uk or blah.contoso.com), you must configure a CNAME record and point the record to landing.phishingbox.com. If you're trying to configure a root domain (such as somecompany.org.uk or comecompany.net), you will need create an A record and point it to (this will auto generate SSL).

To send mail using your custom domain, you will need a TXT record that looks like this:

v=spf1 ip4: -all

Note: If you are configuring a subdomain, you will need to use an A record instead of a CNAME record, as subdomains cannot have both TXT records and CNAME records.

Once the CNAME record or A record has been created, the SPF record has been created, and DNS has had time to propagate the updates, it may be used as a custom domain within PhishingBox.

  • NOTE: DNS may take up to 48 hours to propagate the updates.
  • NOTE: Custom domains can cause an "Insecure Connection" warning in targets' browsers since mail and landing pages will not be served securely.

To add the custom domain to your account, go to Templates > Template Domains and click Add Domain. Enter your domain and click Test Domain. If the CNAME test passes (as shown below), then you'll be able to click Ok and the domain will be visible in your list of Account Domains. Your domain will also need a TXT record in order to be usable on your templates.

Once the domain has the appropriate CNAME and TXT records set up, then you'll be able to use it on your templates. Open the template editor for a phishing email template, expand Completion Settings, and the domain should be visible from the list of domains.


We are aware the system is currently prompting incorrect set up instructions. If you experience this prompt below, please disregard the DNS setup and refer to A record as and TXT record that looks like this: v=spf1 ip4: -all

This error will be fixed in an upcoming deployment.