<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Defaults.Exposed — October 2026 census (v10)</title>
    <link>https://defaults.exposed/</link>
    <atom:link href="https://defaults.exposed/rss.xml" rel="self" type="application/rss+xml" />
    <description>Independent domain-security research: aggregate SPF, DKIM, DMARC, DNSSEC and TLS posture measured across the internet, with as-of dates and public methodology.</description>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>City TLDs ranked: .berlin, .paris, .nyc and .london against their country codes</title>
      <link>https://defaults.exposed/research/city-tlds-ranked</link>
      <guid isPermaLink="true">https://defaults.exposed/research/city-tlds-ranked</guid>
      <description>October 2026: 25 of 26 city, regional and cultural TLDs have a higher F rate than their country code. Six beat it on DMARC enforcement, eight on DNSSEC.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Only 64.5% of domains on Cloudflare nameservers are proxied</title>
      <link>https://defaults.exposed/research/cloudflare-proxied-share</link>
      <guid isPermaLink="true">https://defaults.exposed/research/cloudflare-proxied-share</guid>
      <description>Of 52,954,675 domains on Cloudflare nameservers, 64.5% answered through its proxy, 12.4% without it and 23.1% gave no answer. October 2026 census.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DKIM is not free with hosted mail</title>
      <link>https://defaults.exposed/research/dkim-not-free-with-hosted-mail</link>
      <guid isPermaLink="true">https://defaults.exposed/research/dkim-not-free-with-hosted-mail</guid>
      <description>64.9% of Google Workspace and Microsoft 365 domains had no DKIM key at their provider's selector in the October 2026 census.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>87,922 .gov domains, eight years after the BOD 18-01 deadline</title>
      <link>https://defaults.exposed/research/gov-after-bod-18-01</link>
      <guid isPermaLink="true">https://defaults.exposed/research/gov-after-bod-18-01</guid>
      <description>Of 1,099 live federal executive .gov domains, 89.3% publish DMARC p=reject. Of 1,322 state domains, 14.7% do. October 2026 census.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Money moves by email on domains that can be spoofed</title>
      <link>https://defaults.exposed/research/money-moves-by-email</link>
      <guid isPermaLink="true">https://defaults.exposed/research/money-moves-by-email</guid>
      <description>Of 96,110 domains verified with Stripe, 33.7% enforce DMARC and 55.2% sit at p=none. DocuSign: 61.5%. October 2026 census.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Not a website certificate: EKU, CA flags and missing names</title>
      <link>https://defaults.exposed/research/not-a-website-certificate</link>
      <guid isPermaLink="true">https://defaults.exposed/research/not-a-website-certificate</guid>
      <description>5.0% of 220,326,298 HTTPS leaves still list clientAuth. 3,825,822 are CA, nameless or non-server certificates. October 2026 census.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One mail server and no spare? MX records across 162,982,584 mail domains</title>
      <link>https://defaults.exposed/research/one-mail-server-no-spare</link>
      <guid isPermaLink="true">https://defaults.exposed/research/one-mail-server-no-spare</guid>
      <description>44.5% of gTLD and 56.8% of ccTLD mail domains publish one MX record. At Microsoft 365 that is standard. 31,050,877 name a host of their own.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Security headers that do nothing: 183,766 domains send values the browser throws away</title>
      <link>https://defaults.exposed/research/security-headers-that-do-nothing</link>
      <guid isPermaLink="true">https://defaults.exposed/research/security-headers-that-do-nothing</guid>
      <description>183,766 domains send a security header value the browser discards, from ALLOWALL to SAMEORIGIN; with a stray semicolon. Counted in October 2026.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One private key, 503,418 domains: the shared TLS certificates with the largest blast radius</title>
      <link>https://defaults.exposed/research/shared-certificates-blast-radius</link>
      <guid isPermaLink="true">https://defaults.exposed/research/shared-certificates-blast-radius</guid>
      <description>13.3% of 220,326,298 HTTPS domains present a certificate another apex also presents. One placeholder covers 503,418 of them. October 2026 census.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Mailbox on one platform, sender authorised on another</title>
      <link>https://defaults.exposed/research/spf-vs-mx-vendor-mismatch</link>
      <guid isPermaLink="true">https://defaults.exposed/research/spf-vs-mx-vendor-mismatch</guid>
      <description>7,856,307 domains name one vendor in SPF and another in MX. Most are built that way; 761,259 have a mailbox their SPF record leaves out.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One verification string, many domains: the portfolio census</title>
      <link>https://defaults.exposed/research/verification-token-reuse</link>
      <guid isPermaLink="true">https://defaults.exposed/research/verification-token-reuse</guid>
      <description>October 2026: 97.61% of 37,376,388 account-scoped verification records carry a value no other domain publishes. 16 values sit on over 1,000 domains.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Where a country's email lives: Microsoft, Google and the domestic hosts, by ccTLD</title>
      <link>https://defaults.exposed/research/where-a-countrys-email-lives</link>
      <guid isPermaLink="true">https://defaults.exposed/research/where-a-countrys-email-lives</guid>
      <description>October 2026: Google and Microsoft receive mail for 17.2% of ccTLD mail domains, against 38.6% in the top million. OVHcloud holds 34.8% of .fr.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Who answers for a nation: authoritative DNS dependency by ccTLD</title>
      <link>https://defaults.exposed/research/who-answers-for-a-nation</link>
      <guid isPermaLink="true">https://defaults.exposed/research/who-answers-for-a-nation</guid>
      <description>98.9% of ccTLD domains rely on one DNS operator. Six US operators run nameservers for 28.1%. The 60 largest ccTLDs ranked, October 2026 census.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Whose name is on your certificate? 17,874,769 domains present someone else's</title>
      <link>https://defaults.exposed/research/whose-name-on-your-certificate</link>
      <guid isPermaLink="true">https://defaults.exposed/research/whose-name-on-your-certificate</guid>
      <description>17,874,769 HTTPS domains present a certificate in someone else's name. Ten defaults account for 16.9% of them. October 2026 census.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why the most visited domains on the internet score badly, and what the few A grades do differently</title>
      <link>https://defaults.exposed/research/why-the-most-visited-domains-score-badly</link>
      <guid isPermaLink="true">https://defaults.exposed/research/why-the-most-visited-domains-score-badly</guid>
      <description>We graded the 10,000 most visited domains on the same 33 checks as everyone else. Nearly 7 in 10 fall short of a B and 28.4% score F. What they get wrong, what the 731 A grades share, and why none of it says anything about your domain.</description>
      <pubDate>Sun, 13 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Domain dark matter: 28.8 million domains delegated but never graded</title>
      <link>https://defaults.exposed/research/domain-dark-matter</link>
      <guid isPermaLink="true">https://defaults.exposed/research/domain-dark-matter</guid>
      <description>The October 2026 census scanned 361.3 million domains that exist and graded 332.5 million; the 28.8 million in between never gave a gradable answer.</description>
      <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How domains stack security controls, and where they stop</title>
      <link>https://defaults.exposed/research/how-domains-stack-security-controls</link>
      <guid isPermaLink="true">https://defaults.exposed/research/how-domains-stack-security-controls</guid>
      <description>Most graded domains carry one or two of the five controls the census measures, and 91.7 million publish SPF but no DMARC record.</description>
      <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Ghost towns: where the census's dead domains cluster</title>
      <link>https://defaults.exposed/research/new-gtld-ghost-towns</link>
      <guid isPermaLink="true">https://defaults.exposed/research/new-gtld-ghost-towns</guid>
      <description>In October 2026 three country codes, .tk, .cf and .gq, hold most of the dead domains in the census. Among new gTLDs, .cfd leads, with 10.44% of its names dead.</description>
      <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The locked vault: the 1.3 million domains that close every door</title>
      <link>https://defaults.exposed/research/the-locked-vault</link>
      <guid isPermaLink="true">https://defaults.exposed/research/the-locked-vault</guid>
      <description>1,325,934 domains close all five of SPF, enforced DMARC, DNSSEC, HTTPS and HSTS at once in October 2026: about 1 in 251 of every graded domain.</description>
      <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Contact form emails going to spam</title>
      <link>https://defaults.exposed/fix/contact-form-emails-going-to-spam</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/contact-form-emails-going-to-spam</guid>
      <description>Your web server sends form mail unauthenticated, with no SPF authorisation and no DKIM signature. Route it through authenticated SMTP and the spam stops.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DKIM no key for signature means the selector is missing from DNS</title>
      <link>https://defaults.exposed/fix/dkim-no-key-for-signature</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/dkim-no-key-for-signature</guid>
      <description>No key for signature means the receiver queried s._domainkey.yourdomain and found nothing. Read the s= tag off a real message, publish that record.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DKIM signature not valid, and how to fix it</title>
      <link>https://defaults.exposed/fix/dkim-signature-not-valid</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/dkim-signature-not-valid</guid>
      <description>A DKIM signature that is not valid means the key was found and the check failed. Read the header wording, then the published key, then the signer.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DMARC fails but SPF and DKIM pass, and what to fix</title>
      <link>https://defaults.exposed/fix/dmarc-fails-spf-dkim-pass</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/dmarc-fails-spf-dkim-pass</guid>
      <description>DMARC fails while SPF and DKIM pass because both passed on someone else's domain. Compare header.from with smtp.mailfrom and header.d, then align one leg.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Gmail 550-5.7.1 message blocked, and how to fix it</title>
      <link>https://defaults.exposed/fix/gmail-550-5-7-1</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/gmail-550-5-7-1</guid>
      <description>Gmail 550-5.7.1 is a policy block. The sentence after the code names the cause: your own DMARC, missing reverse DNS on IPv6, or spam filtering.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up SPF, DKIM and DMARC on a new domain</title>
      <link>https://defaults.exposed/fix/new-domain-spf-dkim-dmarc</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/new-domain-spf-dkim-dmarc</guid>
      <description>A new domain needs one SPF record naming your provider, custom-domain DKIM signing, and DMARC p=none with a rua address. About 20 minutes of DNS work.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Newsletter emails failing DMARC? Authenticate your domain</title>
      <link>https://defaults.exposed/fix/newsletter-emails-failing-dmarc</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/newsletter-emails-failing-dmarc</guid>
      <description>Your platform signs as itself, so nothing aligns with your From domain. Turn on its custom domain authentication, add the DKIM CNAMEs, set the bounce domain.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Outlook rejecting your email, 550 5.7.515 and 5.7.509</title>
      <link>https://defaults.exposed/fix/outlook-rejecting-mail</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/outlook-rejecting-mail</guid>
      <description>Consumer Outlook bounces unauthenticated high-volume senders with 550 5.7.515. Exchange Online returns 5.7.509 when your own DMARC policy says reject.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Someone is sending emails from my domain, what to do</title>
      <link>https://defaults.exposed/fix/someone-is-sending-emails-from-my-domain</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/someone-is-sending-emails-from-my-domain</guid>
      <description>Read the From address character by character first. An exact-domain forgery is a DNS fix, a lookalike is a takedown, and they share no steps.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>SPF broke after switching email provider</title>
      <link>https://defaults.exposed/fix/spf-broke-after-switching-provider</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/spf-broke-after-switching-provider</guid>
      <description>The new provider's record went in next to the old one. Two v=spf1 records are a PermError, so merge to one, delete the rest, verify at your nameservers.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CSP adoption has two numbers: which one to cite, and why</title>
      <link>https://defaults.exposed/research/csp-adoption-corrected</link>
      <guid isPermaLink="true">https://defaults.exposed/research/csp-adoption-corrected</guid>
      <description>Citing CSP adoption? 10.45% of domains that sent headers carry a CSP header, and 2.85% carry one that constrains script. Cite the second, with its denominator.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The DMARC records sitting at p=none that never asked for a report</title>
      <link>https://defaults.exposed/research/dmarc-rua</link>
      <guid isPermaLink="true">https://defaults.exposed/research/dmarc-rua</guid>
      <description>rua= is the DMARC tag that names where aggregate reports go. A p=none record without it asks for nothing, so nothing arrives. Add it, then read a fortnight.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Most Content-Security-Policy headers are not content security policies</title>
      <link>https://defaults.exposed/research/does-my-csp-do-anything</link>
      <guid isPermaLink="true">https://defaults.exposed/research/does-my-csp-do-anything</guid>
      <description>Test your own header: a CSP without default-src or script-src constrains no script, and 27.26% of CSP headers in the October 2026 census have either.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>63% of the internet's failing domains are within twenty points of a pass</title>
      <link>https://defaults.exposed/research/f-grade-score-bands</link>
      <guid isPermaLink="true">https://defaults.exposed/research/f-grade-score-bands</guid>
      <description>Got an F on your own scan? Read the score under it: 62.89% of F-graded domains score 40 to 59, within twenty points of the 60 mark where F ends.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What is a google-site-verification TXT record, and how many domains publish one?</title>
      <link>https://defaults.exposed/research/google-site-verification</link>
      <guid isPermaLink="true">https://defaults.exposed/research/google-site-verification</guid>
      <description>A google-site-verification TXT record is an inert ownership proof for a Google property. 30,511,620 domains carry one, and it is safe to leave in place.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How many TXT verification records does one domain carry?</title>
      <link>https://defaults.exposed/research/how-many-txt-records-should-a-domain-have</link>
      <guid isPermaLink="true">https://defaults.exposed/research/how-many-txt-records-should-a-domain-have</guid>
      <description>Most domains with a verification token in DNS carry exactly one; a small band carries three or more, and that's where unaccounted-for records live.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How many domains carry a Microsoft 365 tenant marker, and how many route mail there today?</title>
      <link>https://defaults.exposed/research/microsoft-365-marker-vs-mail-routing</link>
      <guid isPermaLink="true">https://defaults.exposed/research/microsoft-365-marker-vs-mail-routing</guid>
      <description>8,456,816 domains carry an MS= tenant marker; 14,967,920 of 180,564,746 domains with MX route mail to Microsoft 365. The two use different bases.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How many domains have declared themselves to OpenAI?</title>
      <link>https://defaults.exposed/research/openai-domain-verification</link>
      <guid isPermaLink="true">https://defaults.exposed/research/openai-domain-verification</guid>
      <description>241,667 domains publish an openai-domain-verification TXT record at the apex, of the 174,990,877 with any apex TXT record in the October 2026 census.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What the web announces about itself: server and x-powered-by headers</title>
      <link>https://defaults.exposed/research/server-and-x-powered-by-headers</link>
      <guid isPermaLink="true">https://defaults.exposed/research/server-and-x-powered-by-headers</guid>
      <description>The most common Server header is cloudflare, 47,009,028 of 222,969,925 header-sending domains in the October 2026 census, and one config line trims the version from yours.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>87 million domains are three records away from a C</title>
      <link>https://defaults.exposed/research/three-records-away-from-a-c</link>
      <guid isPermaLink="true">https://defaults.exposed/research/three-records-away-from-a-c</guid>
      <description>Do the DMARC policy first, then the SPF fail qualifier, then HSTS. Three records are the shortest route from the top band of F to a C.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>unsafe-inline, and frame-ancestors versus X-Frame-Options: what the web sends</title>
      <link>https://defaults.exposed/research/unsafe-inline-and-frame-ancestors</link>
      <guid isPermaLink="true">https://defaults.exposed/research/unsafe-inline-and-frame-ancestors</guid>
      <description>unsafe-inline silences CSP errors by switching off the script guard; most counted policies only control framing. A nonce or hash restores the guard.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The verification-token census: every third-party token in the internet's DNS, ranked</title>
      <link>https://defaults.exposed/research/verification-token-census</link>
      <guid isPermaLink="true">https://defaults.exposed/research/verification-token-census</guid>
      <description>The ranked table of DNS verification tokens: 46,336,520 domains carry one, out of 174,990,877 with any apex TXT record, over 1434 TLD partitions.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to add a CAA record in Cloudflare</title>
      <link>https://defaults.exposed/setup/caa/cloudflare</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/caa/cloudflare</guid>
      <description>In Cloudflare DNS, add a CAA record with name @, flags 0, tag Only allow specific hostnames, and your CA's domain, such as letsencrypt.org.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Route 53 CAA record setup, step by step</title>
      <link>https://defaults.exposed/setup/caa/route-53</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/caa/route-53</guid>
      <description>In Route 53, create a record with an empty name, type CAA, and value 0 issue &quot;letsencrypt.org&quot;. List every authority you use, including amazon.com for ACM.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DKIM on Beget with a subzone</title>
      <link>https://defaults.exposed/setup/dkim/beget</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dkim/beget</guid>
      <description>In Beget, create a subzone named for your DKIM selector first, then add the TXT or CNAME record your email provider gave you inside it.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DKIM on Cloudflare</title>
      <link>https://defaults.exposed/setup/dkim/cloudflare</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dkim/cloudflare</guid>
      <description>Your mail provider generates the DKIM key; Cloudflare publishes it. Add a TXT record named for the selector alone, and leave your domain off the name.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DKIM on GoDaddy DNS</title>
      <link>https://defaults.exposed/setup/dkim/godaddy</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dkim/godaddy</guid>
      <description>Your mail provider generates the DKIM key; GoDaddy publishes it. Put only the selector in the Name field, save, then hit verify at the provider.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Google Workspace DKIM setup and the record to publish</title>
      <link>https://defaults.exposed/setup/dkim/google-workspace</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dkim/google-workspace</guid>
      <description>Google generates the key in Admin console under Gmail, Authenticate email. Publish it as a TXT record at google._domainkey, then click Start authentication.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DKIM on Microsoft 365</title>
      <link>https://defaults.exposed/setup/dkim/microsoft-365</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dkim/microsoft-365</guid>
      <description>Publish Microsoft's two CNAME records, selector1._domainkey and selector2._domainkey, in your DNS host, then turn DKIM signing on at security.microsoft.com.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DKIM on Reg.ru</title>
      <link>https://defaults.exposed/setup/dkim/reg-ru</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dkim/reg-ru</guid>
      <description>Your email provider generates the DKIM key and selector; you add it as a TXT or CNAME record in the Reg.ru zone editor, using the selector alone as the host.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to add a DKIM record in AWS Route 53</title>
      <link>https://defaults.exposed/setup/dkim/route-53</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dkim/route-53</guid>
      <description>In your Route 53 hosted zone, enter the selector alone as the record name, wrap a TXT key in double quotes, and paste a CNAME target with none.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DMARC on Cloudflare</title>
      <link>https://defaults.exposed/setup/dmarc/cloudflare</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dmarc/cloudflare</guid>
      <description>In Cloudflare DNS, add a TXT record named _dmarc holding v=DMARC1; p=none; rua=mailto:you@yourdomain.com, then raise the policy once the reports look clean.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DMARC on GoDaddy</title>
      <link>https://defaults.exposed/setup/dmarc/godaddy</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dmarc/godaddy</guid>
      <description>Add one TXT record at the host name _dmarc in GoDaddy DNS, starting v=DMARC1; p=none; rua=mailto:, then check it before you tighten the policy.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DMARC on Google Workspace</title>
      <link>https://defaults.exposed/setup/dmarc/google-workspace</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dmarc/google-workspace</guid>
      <description>DMARC for Google Workspace is one TXT record at _dmarc in your DNS host. Google Admin has no DMARC switch. Start at p=none with a rua you read.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to add a DMARC record in Hostinger hPanel</title>
      <link>https://defaults.exposed/setup/dmarc/hostinger</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dmarc/hostinger</guid>
      <description>In hPanel open your domain's DNS zone, add a TXT record named _dmarc with the value v=DMARC1; p=none; rua=mailto:you@yourdomain.com, leave TTL default.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DMARC on Microsoft 365</title>
      <link>https://defaults.exposed/setup/dmarc/microsoft-365</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dmarc/microsoft-365</guid>
      <description>DMARC on Microsoft 365 is a TXT record named _dmarc, added wherever your DNS lives. Start with v=DMARC1; p=none; rua=mailto:you@yourdomain.com.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Reg.ru DMARC record, add it and verify it</title>
      <link>https://defaults.exposed/setup/dmarc/reg-ru</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dmarc/reg-ru</guid>
      <description>In the Reg.ru personal account, add a TXT record with subdomain _dmarc holding v=DMARC1; p=none; rua=mailto:you@yourdomain.com, then confirm it resolves.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DMARC on AWS Route 53</title>
      <link>https://defaults.exposed/setup/dmarc/route-53</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dmarc/route-53</guid>
      <description>In Route 53, create a TXT record named _dmarc with the value in double quotes: &quot;v=DMARC1; p=none; rua=mailto:you@yourdomain.com&quot;, then raise the policy.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up DMARC on Timeweb</title>
      <link>https://defaults.exposed/setup/dmarc/timeweb</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dmarc/timeweb</guid>
      <description>Add a TXT record named _dmarc in Timeweb's DNS editor with the value v=DMARC1; p=none; rua=mailto:you@yourdomain.com, then check for a duplicate.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to add a DMARC record in Wix DNS</title>
      <link>https://defaults.exposed/setup/dmarc/wix</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dmarc/wix</guid>
      <description>In Wix DNS add a TXT record, host name _dmarc, value v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com, then read the reports before you tighten it.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to enable DNSSEC on Reg.ru</title>
      <link>https://defaults.exposed/setup/dnssec/reg-ru</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dnssec/reg-ru</guid>
      <description>DNSSEC at Reg.ru needs Premium DNS and the ns1.reg.ru nameservers. Switch it on in the zone management tab and Reg.ru lodges the keys for you.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up SPF on Beget and add a second sender</title>
      <link>https://defaults.exposed/setup/spf/beget</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/spf/beget</guid>
      <description>Beget publishes v=spf1 redirect=beget.com for you. To add another sender, rewrite that one TXT record in include: form and end it with your own all term.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to add an SPF record in GoDaddy DNS</title>
      <link>https://defaults.exposed/setup/spf/godaddy</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/spf/godaddy</guid>
      <description>Add one TXT record at the apex: name @, value your provider's v=spf1 string, no quotes, one SPF record only. First check GoDaddy runs your DNS.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Hostinger SPF record, and why yours may not work</title>
      <link>https://defaults.exposed/setup/spf/hostinger</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/spf/hostinger</guid>
      <description>Add one TXT record at @ in Hostinger's DNS zone with your provider's SPF value, and only if your nameservers point at Hostinger. One v=spf1 record only.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up SPF on Porkbun</title>
      <link>https://defaults.exposed/setup/spf/porkbun</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/spf/porkbun</guid>
      <description>Add one TXT record in Porkbun's DNS Records, leave Host blank for the root, paste the SPF string with no quotes, and keep it to a single record.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up SPF on Reg.ru</title>
      <link>https://defaults.exposed/setup/spf/reg-ru</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/spf/reg-ru</guid>
      <description>Add one TXT record on host @ carrying your mail provider's include value and an all term, in the Reg.ru panel that matches the domain's nameservers.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>SPF record in AWS Route 53, step by step</title>
      <link>https://defaults.exposed/setup/spf/route-53</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/spf/route-53</guid>
      <description>In Route 53 create a TXT record, leave the record name empty, and type the SPF value inside double quotes. Route 53 does not add the quotes for you.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Timeweb SPF record, how to edit it</title>
      <link>https://defaults.exposed/setup/spf/timeweb</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/spf/timeweb</guid>
      <description>Timeweb publishes v=spf1 include:_spf.timeweb.ru ~all for delegated domains. Edit that record to add your other senders, never add a second one.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The DMARC policy mix across four editions: none, quarantine, reject</title>
      <link>https://defaults.exposed/trends/dmarc-policy-mix</link>
      <guid isPermaLink="true">https://defaults.exposed/trends/dmarc-policy-mix</guid>
      <description>Across four 2026 editions about half of published DMARC records sat at p=none and the policy mix stayed flat. A p=none record changes nothing.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>HSTS and CSP presence across four editions</title>
      <link>https://defaults.exposed/trends/hsts-and-csp-across-three-editions</link>
      <guid isPermaLink="true">https://defaults.exposed/trends/hsts-and-csp-across-three-editions</guid>
      <description>HSTS share of answering domains: 19.89%, 19.11%, 19.24%, 19.57% from July to October 2026; CSP: 7.64%, 7.93%, 8.02%, 8.40%. Counts rose for both; the HSTS share is still below July's.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>TLS 1.3 across four census editions: what moved and what didn't</title>
      <link>https://defaults.exposed/trends/tls-1-3-adoption</link>
      <guid isPermaLink="true">https://defaults.exposed/trends/tls-1-3-adoption</guid>
      <description>TLS 1.3 was negotiated on 94.81%, 94.87%, 94.41% and 94.56% of completed handshakes from July to October 2026; TLS 1.2 on 5.19%, 5.13%, 5.59% and 5.44%.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What we will and will not compare between census editions</title>
      <link>https://defaults.exposed/trends/what-we-compare</link>
      <guid isPermaLink="true">https://defaults.exposed/trends/what-we-compare</guid>
      <description>Two census figures are compared only when both denominators are an observed record set in the same edition; shares of all domains are not compared.</description>
      <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>BIMI needs more than a logo: the DMARC gate in front of it</title>
      <link>https://defaults.exposed/bimi-needs-dmarc</link>
      <guid isPermaLink="true">https://defaults.exposed/bimi-needs-dmarc</guid>
      <description>Your BIMI logo won't render while DMARC says p=none. Receivers check aligned DKIM, then an enforcing DMARC policy, and only then read the BIMI record.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Can someone send email as your domain right now?</title>
      <link>https://defaults.exposed/can-someone-spoof-my-domain</link>
      <guid isPermaLink="true">https://defaults.exposed/can-someone-spoof-my-domain</guid>
      <description>Yes, unless your DMARC record says p=quarantine or p=reject. Anyone can type your domain into a From: line; that record is what makes receivers refuse it.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DKIM: signing, selectors, and the failures you will actually see</title>
      <link>https://defaults.exposed/dkim</link>
      <guid isPermaLink="true">https://defaults.exposed/dkim</guid>
      <description>A dkim=fail line names its own cause: the body changed in transit, a signed header changed, or no key answers at the selector. Each is fixed at the sender or in DNS.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DMARC: what your record instructs a receiver to do</title>
      <link>https://defaults.exposed/dmarc</link>
      <guid isPermaLink="true">https://defaults.exposed/dmarc</guid>
      <description>A DMARC record only changes anything when p= says quarantine or reject. p=none tells every receiver to deliver forged mail as normal and send you a report.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Do subdomains inherit your DMARC policy? The sp= tag nobody sets</title>
      <link>https://defaults.exposed/dmarc-subdomain-policy</link>
      <guid isPermaLink="true">https://defaults.exposed/dmarc-subdomain-policy</guid>
      <description>Subdomains inherit p= unless sp= overrides it. sp=none on a p=reject record delivers forged mail from any subdomain, real or invented. Delete it or set reject.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>quarentine, quarantaine, and the DMARC typos that void a record</title>
      <link>https://defaults.exposed/dmarc-typos</link>
      <guid isPermaLink="true">https://defaults.exposed/dmarc-typos</guid>
      <description>A DMARC record whose p= says quarentine, policy or nothing at all is read as p=none or ignored outright. Find your typo in the ranked list and fix one word.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DNS and DNSSEC: what signing changes and what it breaks</title>
      <link>https://defaults.exposed/dns</link>
      <guid isPermaLink="true">https://defaults.exposed/dns</guid>
      <description>DNSSEC signs your DNS answers so resolvers can reject forged ones. A broken chain makes the domain vanish; 7.0% of domains checked have a valid one.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>SERVFAIL after turning on DNSSEC: signed, broken, or off</title>
      <link>https://defaults.exposed/dnssec-servfail</link>
      <guid isPermaLink="true">https://defaults.exposed/dnssec-servfail</guid>
      <description>SERVFAIL after DNSSEC means the DS at your registrar doesn't match a live key, or the signatures lapsed. Pull the DS to fail open, then repair the chain.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Bounce codes: reading the rejection your receiver actually sent</title>
      <link>https://defaults.exposed/email-delivery</link>
      <guid isPermaLink="true">https://defaults.exposed/email-delivery</guid>
      <description>Your bounce names the reason in a code like 550 5.7.26. Match the code here, open the page that fixes it, and check your domain free before the next send.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to find the DKIM selector your provider uses</title>
      <link>https://defaults.exposed/find-your-dkim-selector</link>
      <guid isPermaLink="true">https://defaults.exposed/find-your-dkim-selector</guid>
      <description>Your DKIM selector is the s= tag in the DKIM-Signature header of a message you send. Read it from a raw message, then look it up under _domainkey in DNS.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>550-5.7.26 This email has been blocked because the sender is unauthenticated</title>
      <link>https://defaults.exposed/fix/550-5-7-26-sender-is-unauthenticated</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/550-5-7-26-sender-is-unauthenticated</guid>
      <description>Gmail sends 550-5.7.26 when a message fails both SPF and DKIM. Get either one passing for the sending domain and the block clears once DNS is visible.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DKIM &quot;body hash did not verify&quot;</title>
      <link>https://defaults.exposed/fix/dkim-body-hash-did-not-verify</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/dkim-body-hash-did-not-verify</guid>
      <description>Body hash did not verify means something rewrote your message after it was signed; find the gateway, appliance, list or relay that edits it and sign after that hop.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>p=none, p=quarantine, p=reject: what each one tells a receiver</title>
      <link>https://defaults.exposed/fix/dmarc-policy-none-vs-reject</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/dmarc-policy-none-vs-reject</guid>
      <description>p=none reports and delivers, p=quarantine sends failures to junk, p=reject refuses them. Move up in that order, one free DNS edit at a time.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DMARC quarantine/reject policy not enabled: answering the scanner finding</title>
      <link>https://defaults.exposed/fix/dmarc-quarantine-reject-policy-not-enabled</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/dmarc-quarantine-reject-policy-not-enabled</guid>
      <description>The warning means no DMARC record or a record at p=none. Publish v=DMARC1; p=none; rua= today, read the reports, then step to quarantine and reject.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Mail forwarding breaks SPF, and what survives it</title>
      <link>https://defaults.exposed/fix/forwarding-breaks-spf</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/forwarding-breaks-spf</guid>
      <description>Forwarded mail fails SPF because the forwarder sends from an IP you never listed; no record fixes that, and DKIM signed with your own domain is what survives.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Is .com safer than .net or .org? The measured answer with the denominator stated</title>
      <link>https://defaults.exposed/fix/is-com-safer-than-net-or-org</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/is-com-safer-than-net-or-org</guid>
      <description>On the October 2026 census .net carries the highest F share of the legacy three and .com the lowest; the gap measures who buys each ending.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>No SPF record found: what the checker means and what to publish</title>
      <link>https://defaults.exposed/fix/no-spf-record-found</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/no-spf-record-found</guid>
      <description>No SPF record found is urgent if your domain accepts mail. Check MX, count the v=spf1 lines at the authoritative nameserver, then publish one or merge to one.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Not secure: the five things that put that label on your site</title>
      <link>https://defaults.exposed/fix/not-secure</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/not-secure</guid>
      <description>Not secure means the browser couldn't trust the page: no HTTPS, an expired, mismatched or untrusted certificate, or one http:// asset on a valid HTTPS page.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>SPF failing for a SaaS sender in Europe: alignment or the lookup cliff</title>
      <link>https://defaults.exposed/fix/spf-failing-saas-europe</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/spf-failing-saas-europe</guid>
      <description>When a SaaS tool fails SPF, read Return-Path against Authentication-Results: usually SPF passed on the vendor's domain and DMARC failed alignment.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>SPF PermError: too many DNS lookups, and how to get back under ten</title>
      <link>https://defaults.exposed/fix/spf-permerror-too-many-dns-lookups</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/spf-permerror-too-many-dns-lookups</guid>
      <description>Past ten DNS lookups a receiver returns PermError and voids your whole SPF record. Count the resolved chain, prune dead includes, use subdomains.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>554 5.7.9 Message not accepted for policy reasons</title>
      <link>https://defaults.exposed/fix/yahoo-554-5-7-9</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/yahoo-554-5-7-9</guid>
      <description>554 5.7.9 is Yahoo's permanent policy rejection: SPF or DKIM must pass for a domain matching your From address. Test four causes in order, then fix DNS.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Your connection is not private: which of the five certificate faults you have</title>
      <link>https://defaults.exposed/fix/your-connection-is-not-private</link>
      <guid isPermaLink="true">https://defaults.exposed/fix/your-connection-is-not-private</guid>
      <description>The browser can't trust the site's certificate. Match the NET::ERR_ code under the warning to one of five faults, then fix that one, free, in an afternoon.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why gappssmtp.com is signing your mail</title>
      <link>https://defaults.exposed/gappssmtp-signing</link>
      <guid isPermaLink="true">https://defaults.exposed/gappssmtp-signing</guid>
      <description>Google signs your mail as gappssmtp.com because your own DKIM key was never published; publish the record in DNS and the signature moves to your domain.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The October 2026 edition: how 361,301,790 domains were counted</title>
      <link>https://defaults.exposed/how-the-domains-were-counted</link>
      <guid isPermaLink="true">https://defaults.exposed/how-the-domains-were-counted</guid>
      <description>The October 2026 census scanned 632,901,201 of 649,194,272 sourced names, removed 271,599,411 that answered NXDOMAIN, and counts 361,301,790 domains, 332,492,319 of them graded.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How the grade is built: 33 checks, 100 points, and the 40 that email carries</title>
      <link>https://defaults.exposed/how-the-grade-is-built</link>
      <guid isPermaLink="true">https://defaults.exposed/how-the-grade-is-built</guid>
      <description>A domain grade is a score out of 100 from 24 scored checks, with 40 points on email; F is the grade of 74.3% of the 332,492,319 domains that carry one.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>HSTS: the header most HTTPS sites still skip</title>
      <link>https://defaults.exposed/hsts</link>
      <guid isPermaLink="true">https://defaults.exposed/hsts</guid>
      <description>Send Strict-Transport-Security: max-age=31536000; includeSubDomains over HTTPS, ramp max-age up in stages, and the browser stops sending plaintext first.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>HTTP security headers: what each one does and what the web actually sets</title>
      <link>https://defaults.exposed/http-headers</link>
      <guid isPermaLink="true">https://defaults.exposed/http-headers</guid>
      <description>Each HTTP security header, the attack it stops, the share of the web that sets it, and a one-line verdict on whether the audit finding is real or pedantic.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>'may be forged' in your headers is a reverse DNS problem, not a spoofing alert</title>
      <link>https://defaults.exposed/may-be-forged</link>
      <guid isPermaLink="true">https://defaults.exposed/may-be-forged</guid>
      <description>'(may be forged)' means the receiving server could not confirm the sending IP's reverse DNS. The fix is a PTR record at the IP's owner, not a DMARC record.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A parked domain sends no mail and can still be spoofed</title>
      <link>https://defaults.exposed/parked-domain-spoofing</link>
      <guid isPermaLink="true">https://defaults.exposed/parked-domain-spoofing</guid>
      <description>A domain that sends no mail still needs SPF -all and DMARC p=reject, because receivers can't tell it's parked; a null MX is the optional third record.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DKIM on Namecheap: where the key comes from and where it goes</title>
      <link>https://defaults.exposed/setup/dkim/namecheap</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/dkim/namecheap</guid>
      <description>Generate the key in your mail provider's console, then add it in Namecheap Advanced DNS: selector only in Host, the whole value pasted, no quotes.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>SPF for Wix, and the records Wix does not publish for you</title>
      <link>https://defaults.exposed/setup/spf/wix</link>
      <guid isPermaLink="true">https://defaults.exposed/setup/spf/wix</guid>
      <description>Wix holds your DNS and serves the site. SPF, DKIM and DMARC come from your mail provider, and you add them in Wix DNS at @, the selector and _dmarc.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>SPF: what your record says, how it fails, and how to fix it</title>
      <link>https://defaults.exposed/spf</link>
      <guid isPermaLink="true">https://defaults.exposed/spf</guid>
      <description>An SPF record is a DNS TXT line naming the servers allowed to send as your domain. Read yours, match the error in your headers, fix it in minutes.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Should your SPF record end in ~all or -all, and what +all authorises</title>
      <link>https://defaults.exposed/spf-all-qualifier</link>
      <guid isPermaLink="true">https://defaults.exposed/spf-all-qualifier</guid>
      <description>-all lets receivers reject on SPF alone, which can bounce forwarded mail before DKIM is checked; ~all leaves the decision to DMARC. +all authorises anyone on the internet to send as you.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Answering the email-authentication questions on a supplier or insurance questionnaire</title>
      <link>https://defaults.exposed/supplier-questionnaire-email-authentication</link>
      <guid isPermaLink="true">https://defaults.exposed/supplier-questionnaire-email-authentication</guid>
      <description>Pull three DNS records, read the p= tag, write the sentence a reviewer can verify with the same lookup, and attach the free scan as the evidence.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>TLS and certificates: every browser warning and what causes it</title>
      <link>https://defaults.exposed/tls</link>
      <guid isPermaLink="true">https://defaults.exposed/tls</guid>
      <description>Match the exact browser error code to its cause (expired, wrong name, untrusted issuer, dead handshake) and fix each one with the command shown.</description>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
