redirect.pizza works with standard DNS records. Which one you need depends on the hostname you're redirecting. The exact records for each hostname are shown under Hostnames in your account.
CNAME
Use a CNAME record whenever you can. It works for every hostname that isn't the apex, such as www.example.com or test.example.com. A CNAME covers both IPv4 and IPv6.
edge.redirect.pizza
A (IPv4)
The A record is required for apex hostnames (non-www), such as example.com, because DNS doesn't allow a CNAME on the apex.
89.106.200.1
AAAA (IPv6)
Add an AAAA record next to the A record for full IPv6 support. A CNAME already includes both, so this is only needed for apex hostnames.
2a12:5240::1
ALIAS or ANAME
Some DNS providers offer an ALIAS or ANAME record: a CNAME-like record that's allowed on the apex. If your provider supports it, you can point the apex at edge.redirect.pizza with it. The record resolves to our IP addresses, which is what we check.
MX and SPF for email forwarding
When you use email forwarding, add the following MX records:
mx1.redirect.pizza (priority 10) mx2.redirect.pizza (priority 20)
And the following SPF record, as a TXT record:
v=spf1 include:spf.redirect.pizza -all
CAA
If your domain has CAA records, they must allow the certificate authorities we use: Let's Encrypt and ZeroSSL (issued by Sectigo). Without that, we can't issue an SSL certificate for your hostname.
If your domain doesn't have any CAA records, you don't need to add these.
If you are using CAA records, at least the following must be added:
0 issue "letsencrypt.org" 0 issue "sectigo.com"
If you want to use wildcard subdomains, issuewild CAA records are required as well:
0 issuewild "letsencrypt.org" 0 issuewild "sectigo.com"