<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: kiwitoolkit</title>
    <description>The latest articles on DEV Community by kiwitoolkit (@kiwitoolkit).</description>
    <link>https://dev.to/kiwitoolkit</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210237%2Fbd772bfc-63cc-40cf-8af2-33a23bc7a562.png</url>
      <title>DEV Community: kiwitoolkit</title>
      <link>https://dev.to/kiwitoolkit</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kiwitoolkit"/>
    <language>en</language>
    <item>
      <title>I got tired of checking ten SEO dashboards, so I built one weekly to-do list</title>
      <dc:creator>kiwitoolkit</dc:creator>
      <pubDate>Thu, 12 Nov 2026 09:06:25 +0000</pubDate>
      <link>https://dev.to/kiwitoolkit/i-got-tired-of-checking-ten-seo-dashboards-so-i-built-one-weekly-to-do-list-481h</link>
      <guid>https://dev.to/kiwitoolkit/i-got-tired-of-checking-ten-seo-dashboards-so-i-built-one-weekly-to-do-list-481h</guid>
      <description>&lt;p&gt;&lt;em&gt;How I built the SEO/GEO workspace in KiwiToolkit, and why it doesn't try to automate your SEO for you.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I build and run websites. For years, "doing SEO" on them looked the same: Search Console open in one tab, Google Analytics in another, Bing Webmaster Tools somewhere behind them, a PageSpeed report, a crawler export, a rank tracker, and a spreadsheet of sites I'd asked for a link (and who had actually answered).&lt;/p&gt;

&lt;p&gt;Every tool reported its own metrics, in its own way, on its own schedule. None of them answered the only question I actually had on a Monday morning:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How am I doing, and what should I fix this week?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;So most weeks, nothing got checked. Not because I didn't care, but because getting a clear picture took an hour of tab-switching before I could do anything useful.&lt;/p&gt;

&lt;p&gt;That's why I built the SEO Analytics workspace inside &lt;a href="https://kiwitoolkit.com" rel="noopener noreferrer"&gt;KiwiToolkit&lt;/a&gt;. It's available to anyone with a registered account, and there's a free plan you can use on a real site.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem with "AI does your SEO"
&lt;/h2&gt;

&lt;p&gt;Right now every second SEO product promises to automate everything: generate a hundred articles a week, spin up backlinks across the internet, "rank on autopilot".&lt;/p&gt;

&lt;p&gt;I don't believe in that. I've seen what it leaves behind: thin pages nobody reads, and trashy backlinks on sites that exist only to sell links. Search engines get better at ignoring that every year, and AI answer engines are even less forgiving. They cite sources that look trustworthy, not sources that are loud.&lt;/p&gt;

&lt;p&gt;My view is simple: &lt;strong&gt;quality matters more than quantity.&lt;/strong&gt; One relevant link from a real site in your niche beats fifty from a link farm. One page that answers a question well beats ten that rephrase the same keywords.&lt;/p&gt;

&lt;p&gt;So KiwiToolkit deliberately doesn't automate everything. It doesn't write your content and it doesn't buy links. What it does is the part that &lt;em&gt;should&lt;/em&gt; be automated: collecting data from every source into one place, checking things in the background, and turning all of it into a short, prioritised plan. The decisions and the actual work stay with you.&lt;/p&gt;

&lt;h2&gt;
  
  
  One place for all your data
&lt;/h2&gt;

&lt;p&gt;You connect your sources once. After that, the checking happens in the background. Here's what can be connected today:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Google Search Console&lt;/strong&gt;: clicks, impressions, queries and positions, plus Google's own indexing verdict for each page (URL Inspection) and the status of your sitemaps.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google Analytics 4&lt;/strong&gt;: live visitors for every site on one "live board" (works on a phone, or on a TV on the office wall).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bing Webmaster Tools&lt;/strong&gt;: the backlinks pointing at your site.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PageSpeed Insights&lt;/strong&gt;: Lighthouse lab tests of your top pages, on mobile and desktop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Chrome UX Report&lt;/strong&gt;: Core Web Vitals from real Chrome users, with weekly history.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your own sitemap and robots.txt&lt;/strong&gt;: the starting point for a page-by-page site audit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open PageRank&lt;/strong&gt;: an authority score for every site that links to you, so you can tell a strong link from a weak one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DataForSEO&lt;/strong&gt; (paid plans): competitor rankings, keyword gaps, a second backlink index, and the backlink gap (sites that link to your competitors but not to you).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Claude (Anthropic)&lt;/strong&gt;: AI briefs and advice, grounded in the data above. Plans include a number of AI runs, or you can add your own Anthropic key for unlimited use.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'm also working on a browser extension that sends Search Console's Links report into the same Backlinks view.&lt;/p&gt;

&lt;p&gt;A note on trust, since this is your data: Search Console and GA4 are read with read-only access, and you prove you own each domain with a DNS TXT record before anything syncs. You can export or delete everything from your account page.&lt;/p&gt;

&lt;h2&gt;
  
  
  "This week": the page I actually open
&lt;/h2&gt;

&lt;p&gt;This is the heart of the tool and the reason I built it. Every site gets a &lt;strong&gt;This week&lt;/strong&gt; list: &lt;strong&gt;at most seven tasks&lt;/strong&gt;, picked from everything on file and sorted by what matters most.&lt;/p&gt;

&lt;p&gt;The order is intentional:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Blockers first.&lt;/strong&gt; Lost Search Console access, a crawler that's blocked by bot protection, an unverified domain. Nothing else matters until these are fixed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Things that are broken.&lt;/strong&gt; The biggest site audit errors, pages Google refuses to index (grouped by the reason), canonical mismatches, sitemap errors, the worst failing Core Web Vital on phones.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Traffic changes.&lt;/strong&gt; The two biggest click drops of the last seven days, so you find out &lt;em&gt;why&lt;/em&gt; &lt;code&gt;/pricing&lt;/code&gt; lost 96 clicks before it becomes a trend.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quick wins.&lt;/strong&gt; "Striking distance" queries that sit just off page one, pages with a click-through rate well below what their position should get, and two of your pages competing for the same query (cannibalisation).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Links.&lt;/strong&gt; Recently lost backlinks, plus one habit that's always on the list: &lt;em&gt;get one new backlink&lt;/em&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The list is picked on your first visit of the week and then stays put, so it doesn't reshuffle while you're working through it. Next week it's rebuilt from fresh data: fixed problems drop off and new ones show up. Each task links straight to the page that explains it, so you don't have to dig through reports.&lt;/p&gt;

&lt;p&gt;Seven tasks is a deliberate limit. A list of 300 "issues" isn't a plan, it's homework you'll never start.&lt;/p&gt;

&lt;h2&gt;
  
  
  A plan for backlinks, not a link-building machine
&lt;/h2&gt;

&lt;p&gt;This is the part that reflects my "quality over quantity" view most directly.&lt;/p&gt;

&lt;p&gt;The &lt;strong&gt;Backlinks&lt;/strong&gt; tab shows the links you already have (from Bing and, on paid plans, DataForSEO), and &lt;strong&gt;it checks them&lt;/strong&gt;. Every link is opened and verified: is it still there, what's the anchor text, is it nofollow? A link that's missing twice, a day apart, is marked lost. Each linking site gets a strength score, so you can see which links actually carry weight.&lt;/p&gt;

&lt;p&gt;Then there's the &lt;strong&gt;outreach list&lt;/strong&gt;, which replaced my old spreadsheet:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Add the sites you want a link from: a URL, a domain, or a row from the backlink gap (sites that link to your competitors but not to you).&lt;/li&gt;
&lt;li&gt;Move each one through the stages: &lt;strong&gt;to get → asked → published&lt;/strong&gt;, or &lt;strong&gt;dropped&lt;/strong&gt;, with a comment history so you remember what you said to whom.&lt;/li&gt;
&lt;li&gt;Once you mark a link as published, the tool &lt;strong&gt;checks daily that it really went live&lt;/strong&gt;, and after that rechecks it every week.&lt;/li&gt;
&lt;li&gt;Every week, three outreach entries you haven't touched in a while show up on your This week list. A long list rotates, so nobody gets forgotten.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No automated spam, no mass link buying. Just a structured way to earn a few good links every week and make sure they stay.&lt;/p&gt;

&lt;h2&gt;
  
  
  A site audit you can act on
&lt;/h2&gt;

&lt;p&gt;The audit reads your robots.txt and sitemap, then checks every page against a long list of rules: status codes and redirects, noindex and robots blocks, canonicals, titles and meta descriptions (length &lt;em&gt;and&lt;/em&gt; pixel width), headings, thin and duplicate content, readability, image alt text and sizes, internal links and orphan pages, broken links, hreflang, structured data (JSON-LD), Open Graph tags, security headers and mixed content.&lt;/p&gt;

&lt;p&gt;Two details I'm particularly happy with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Every issue has a "Copy AI prompt" button.&lt;/strong&gt; It packs the problem, the hint and what the audit actually read from the page into a ready-made prompt for your AI assistant. AI helps with the fix, and you stay in control of what ships.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It checks that it can get in first.&lt;/strong&gt; If Cloudflare or a security plugin blocks crawlers, you get one clear message telling you so, instead of an audit full of nothing but "blocked" pages.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Alongside the audit, &lt;strong&gt;Google indexing&lt;/strong&gt; shows Google's own view of each page (indexed or not, why, and which canonical Google chose), and &lt;strong&gt;Page speed&lt;/strong&gt; shows real-user Core Web Vitals next to lab tests. Lab numbers are always labelled as lab numbers, so you never confuse a Lighthouse score with what visitors actually experience.&lt;/p&gt;

&lt;h2&gt;
  
  
  Understanding &lt;em&gt;why&lt;/em&gt; traffic moved
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;Growth&lt;/strong&gt; view compares equal periods (7 days, 28 days, 3 months, year on year) and lists the pages and queries that rose, fell, appeared or vanished. For each change, it tries to explain the reason: a better or worse ranking, more or less search demand, a change in click-through rate, a new or lost query, or two of your pages competing with each other.&lt;/p&gt;

&lt;p&gt;One thing I was strict about: Search Console hides some queries for privacy reasons, so a page's real totals are bigger than the sum of its query rows. When most of a change comes from those hidden queries, the tool says so plainly instead of making up an explanation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where AI fits in
&lt;/h2&gt;

&lt;p&gt;I use AI where it's genuinely good: reading a lot of numbers and saying what stands out.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Weekly brief.&lt;/strong&gt; Every Monday, a short summary of what moved on each site and what to look at first. It takes two minutes to read.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Page advice.&lt;/strong&gt; Pick a page and get specific, small suggestions for improving it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Competitor ideas.&lt;/strong&gt; Based on your top searches and pages, it proposes sites you actually compete with. A suggestion only appears once real ranking data confirms the site exists and ranks in your market, because AI models sometimes invent domains.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The AI is instructed to use only the numbers in your data, never to invent metrics, and to back every recommendation with a reason from that data. It's an advisor that points you in a direction, not an autopilot.&lt;/p&gt;

&lt;h2&gt;
  
  
  Competitors and opportunities
&lt;/h2&gt;

&lt;p&gt;On paid plans, the &lt;strong&gt;Competitors&lt;/strong&gt; view shows two different things that are easy to mix up:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Market size&lt;/strong&gt;: how big each competitor really is across their whole domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Share of your keywords&lt;/strong&gt;: who wins the specific searches &lt;em&gt;you&lt;/em&gt; care about, taken from your own Search Console data.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Opportunities&lt;/strong&gt; merges every competitor's keyword gaps into one list ranked by search volume, next to your own striking-distance queries. Striking distance works on the free plan too, because it only needs Search Console.&lt;/p&gt;

&lt;h2&gt;
  
  
  And GEO?
&lt;/h2&gt;

&lt;p&gt;More and more people get answers from ChatGPT, Perplexity, Gemini or Google's AI Overviews instead of a list of ten blue links. That's what people mean by GEO (generative engine optimisation).&lt;/p&gt;

&lt;p&gt;I don't think GEO replaces SEO. It raises the bar on the same fundamentals: AI answer engines can only cite pages they can crawl and understand, and they prefer sources that other trustworthy sites point to. Crawlable, indexed pages, a clear heading structure, valid structured data, content that's actually useful, and real links from real sites. Those are exactly the things KiwiToolkit tracks and puts on your weekly list.&lt;/p&gt;

&lt;p&gt;The trashy backlinks and mass-produced pages that sometimes still squeeze out a ranking are much less likely to get you cited by an AI. Quality wins here even more clearly than it does in classic search.&lt;/p&gt;

&lt;h2&gt;
  
  
  The weekly routine
&lt;/h2&gt;

&lt;p&gt;Here's what using it actually looks like:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Monday:&lt;/strong&gt; read the brief. Two minutes on what moved and why.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open "This week":&lt;/strong&gt; a handful of tasks, most urgent first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fix and move on:&lt;/strong&gt; each task says what's wrong and where.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Next week:&lt;/strong&gt; the list is rebuilt from fresh data.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;In the background: new Search Console data and Google's indexing status every morning, backlinks rechecked weekly (published outreach links daily), page speed tested every Saturday, and audited sites re-audited every Sunday.&lt;/p&gt;

&lt;h2&gt;
  
  
  It's still growing, and I'd love your feedback
&lt;/h2&gt;

&lt;p&gt;KiwiToolkit is a project I build myself, and the SEO workspace ships new features almost every week. The This week list, the outreach list, the live board, indexing and page speed checks all landed in the last couple of weeks, and there's more coming.&lt;/p&gt;

&lt;p&gt;If you run a site, a blog, a shop or a side project, &lt;strong&gt;give it a try&lt;/strong&gt;. Every account starts on a free plan that runs the same app on one real site, with no card and no trial clock. Setup takes a few minutes: connect Search Console, add a DNS record, and next Monday you'll know what to fix first.&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://kiwitoolkit.com/seo-analytics" rel="noopener noreferrer"&gt;Try SEO Analytics on KiwiToolkit&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I'd really appreciate your feedback:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What do you check every week that's missing here?&lt;/li&gt;
&lt;li&gt;Which data sources should I connect next?&lt;/li&gt;
&lt;li&gt;What would you want from GEO checks specifically?&lt;/li&gt;
&lt;li&gt;Did the This week list point at something worth fixing on your site, or at noise?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Leave a comment below or reach out through the site. Every suggestion gets read, and quite a few of the features above started as someone's "it would be nice if…".&lt;/p&gt;

&lt;p&gt;Thanks for reading, and good luck with your sites! 🥝&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>ai</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Why your emails land in spam: a practical SPF, DKIM and DMARC checklist</title>
      <dc:creator>kiwitoolkit</dc:creator>
      <pubDate>Tue, 27 Oct 2026 07:54:15 +0000</pubDate>
      <link>https://dev.to/kiwitoolkit/why-your-emails-land-in-spam-a-practical-spf-dkim-and-dmarc-checklist-43p8</link>
      <guid>https://dev.to/kiwitoolkit/why-your-emails-land-in-spam-a-practical-spf-dkim-and-dmarc-checklist-43p8</guid>
      <description>&lt;p&gt;Your app sends a password reset. The user never gets it. Nothing errors on your side: the receiving server simply decided your mail wasn't trustworthy.&lt;/p&gt;

&lt;p&gt;Most of the time the cause is three DNS records: &lt;strong&gt;SPF&lt;/strong&gt;, &lt;strong&gt;DKIM&lt;/strong&gt; and &lt;strong&gt;DMARC&lt;/strong&gt;. Here's what each one does and the mistakes that break them.&lt;/p&gt;

&lt;h2&gt;
  
  
  SPF: who is allowed to send as you
&lt;/h2&gt;

&lt;p&gt;SPF is a TXT record listing the servers allowed to send mail for your domain:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;v=spf1 include:_spf.google.com include:sendgrid.net -all
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Mistake 1: going over 10 DNS lookups.&lt;/strong&gt; Each &lt;code&gt;include:&lt;/code&gt;, &lt;code&gt;a&lt;/code&gt;, &lt;code&gt;mx&lt;/code&gt; and &lt;code&gt;redirect&lt;/code&gt; costs at least one lookup, and includes can contain more includes. Go over 10 and SPF returns a &lt;code&gt;permerror&lt;/code&gt;. Many receivers then treat your mail as failing SPF. This happens slowly as you add tools, so nobody notices.&lt;/p&gt;

&lt;p&gt;Fix: remove includes for services you no longer use, and prefer &lt;code&gt;ip4:&lt;/code&gt;/&lt;code&gt;ip6:&lt;/code&gt; entries where a provider gives you fixed IPs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Mistake 2: two SPF records.&lt;/strong&gt; You can have exactly one &lt;code&gt;v=spf1&lt;/code&gt; TXT record. Merge them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Mistake 3: &lt;code&gt;+all&lt;/code&gt;.&lt;/strong&gt; That allows anyone to send as you. Use &lt;code&gt;-all&lt;/code&gt; (fail) or &lt;code&gt;~all&lt;/code&gt; (softfail).&lt;/p&gt;

&lt;h2&gt;
  
  
  DKIM: proving the message wasn't changed
&lt;/h2&gt;

&lt;p&gt;Your sending service signs every message, and the public key lives at &lt;code&gt;selector._domainkey.yourdomain.com&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Mistake: adding a sending tool and never setting up its DKIM.&lt;/strong&gt; Every service that sends as your domain (CRM, newsletter, helpdesk, transactional email) needs its own DKIM record. Look up its docs for the selector and CNAME/TXT value.&lt;/p&gt;

&lt;p&gt;Also watch for an empty &lt;code&gt;p=&lt;/code&gt; in a DKIM record. That means the key was revoked.&lt;/p&gt;

&lt;h2&gt;
  
  
  DMARC: what to do when checks fail
&lt;/h2&gt;

&lt;p&gt;DMARC ties SPF and DKIM to the visible From: domain and tells receivers what to do with failures:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;_dmarc.yourdomain.com  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Mistake: leaving it on &lt;code&gt;p=none&lt;/code&gt; forever.&lt;/strong&gt; &lt;code&gt;none&lt;/code&gt; is monitoring only and blocks nothing. The usual rollout:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;p=none&lt;/code&gt; with &lt;code&gt;rua=&lt;/code&gt; reporting turned on. Read the reports for a few weeks.&lt;/li&gt;
&lt;li&gt;Fix every legitimate sender that fails.&lt;/li&gt;
&lt;li&gt;Move to &lt;code&gt;p=quarantine&lt;/code&gt;, then &lt;code&gt;p=reject&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  While you're there: TLS and headers
&lt;/h2&gt;

&lt;p&gt;Two more cheap checks: make sure your certificate isn't close to expiry (auto-renewal fails more often than you'd think), and that plain HTTP redirects to HTTPS.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checking all of it at once
&lt;/h2&gt;

&lt;p&gt;You can check each record with &lt;code&gt;dig&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dig +short TXT yourdomain.com
dig +short TXT _dmarc.yourdomain.com
dig +short TXT google._domainkey.yourdomain.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or, if you'd rather get one page: I built a free &lt;a href="https://kiwitoolkit.com/domain-report" rel="noopener noreferrer"&gt;domain report&lt;/a&gt; that checks SPF (including the lookup count), DKIM on common selectors, DMARC, TLS and security headers in one pass. There's also an &lt;a href="https://kiwitoolkit.com/spf-dkim-dmarc-builder" rel="noopener noreferrer"&gt;SPF/DKIM/DMARC record builder&lt;/a&gt; if you're writing records from scratch. No sign-up, nothing stored.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Exactly one SPF record, under 10 lookups, ending in &lt;code&gt;-all&lt;/code&gt; or &lt;code&gt;~all&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] DKIM set up for &lt;strong&gt;every&lt;/strong&gt; service that sends as your domain&lt;/li&gt;
&lt;li&gt;[ ] DMARC record exists, with reporting on&lt;/li&gt;
&lt;li&gt;[ ] A plan to move DMARC from &lt;code&gt;none&lt;/code&gt; → &lt;code&gt;quarantine&lt;/code&gt; → &lt;code&gt;reject&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] TLS certificate not expiring soon; HTTP redirects to HTTPS&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What's the strangest deliverability problem you've debugged? Tell me in the comments.&lt;/p&gt;

</description>
      <category>email</category>
      <category>dns</category>
      <category>webdev</category>
      <category>security</category>
    </item>
  </channel>
</rss>
