FAQ
Frequently asked
questions
Quick answers to the most common questions.
Privacy & Security
Your data
Does my CSV file get uploaded anywhere?
No. The file never leaves your browser. It is read using the JavaScript File API and processed entirely
client-side. There is no server, no backend, and no network request is made with your data.
Is this tool affiliated with AWS or Cloudflare?
No. This is an independent open source tool built to bridge a gap between two services. It has no official
relationship with Amazon Web Services or Cloudflare.
Is it open source?
Yes. The source code is available on
GitHub
under the
MIT License
.
Using the Tool
Common questions
Where do I find the CSV in AWS SES?
Go to
SES → Configuration → Identities
, select your domain, open the
Authentication
tab, scroll to
DomainKeys Identified Mail (DKIM) → Publish DNS records
, and click
Download .csv record set
. This works whether the domain is already verified or newly added.
The tool shows an error about missing columns. What's wrong?
The CSV must have a header row with exactly three columns:
Type
,
Name
, and
Value
(case-insensitive). If you opened and re-saved the CSV in Excel or Numbers, the file may have been
reformatted. Try re-downloading it directly from the AWS console.
The filename says "example.com" instead of my domain. Why?
The tool detects your domain from the
Name
column by stripping the
_domainkey
subdomain prefix. If your CSV has an unexpected format in that column, detection may fall back to a
placeholder. The zone file content is still correct — you can rename the downloaded file manually.
Can I use this for DNS records other than SES DKIM?
Yes. The tool works with any CSV that has
Type
,
Name
, and
Value
columns. It does not filter by record type — CNAME, TXT, MX, and others are all passed through.
What if my CSV has records for multiple domains?
All records are included in the output. The domain shown in the zone file header comment is taken from the
first record. You can split the output manually if needed.
After Import
Verification & DNS
I imported the zone file but DKIM isn't verified in SES yet. What now?
DNS propagation takes time. AWS SES checks periodically and can take anywhere from a few minutes to 72
hours to detect new records. You don't need to do anything — just wait. You can monitor the status under
SES → Configuration → Identities → Authentication tab
.
Why is TTL set to 1 in the zone file?
1
is Cloudflare's magic value for automatic TTL. After import, Cloudflare replaces it with its own default
(usually 300s or "Auto"). You can change it manually in the DNS panel after import if needed.
Cloudflare says some records already exist on import. What do I do?
Cloudflare will skip duplicates and warn you. This is safe — it just means those records were already in
your zone. Review the import preview and confirm.