Skip to main content
InfoDNS

How to fix: SOA Serial Looks Stale (Date-Based Convention)

The SOA serial number follows the common YYYYMMDDnn convention and decodes to a date more than 3 years in the past. This is a soft, informational signal: not every DNS provider uses a date-based serial, and a stable serial does not necessarily mean the zone is unmaintained.

Why it matters

On its own this is not a vulnerability. It can be a hint that the zone is managed by hand rather than through an automated provider, worth a second look if other DNS hygiene findings are also present.

Many self-hosted DNS setups (BIND, cPanel, and similar) follow the YYYYMMDDnn serial convention, incrementing the trailing two digits on every edit within a day. When that number decodes to a genuine calendar date several years old, it suggests the zone hasn't been edited through that convention in a long time. Managed DNS providers (Cloudflare, Route 53, NS1) generally use their own serial scheme unrelated to calendar dates, so this check only fires when the serial actually parses as a real, plausible date.

How to fix it

  1. 1No action is required solely because of this finding.
  2. 2If the zone is genuinely unmaintained, review all records (SPF, DMARC, CAA, stale CNAMEs) for accuracy rather than just bumping the serial.

Code examples

SOA serial convention

DNS
example.com. IN SOA ns1.example.com. hostmaster.example.com. (
  2026081001 ; serial: YYYYMMDDnn, bump on every edit
  3600       ; refresh
  900        ; retry
  604800     ; expire
  300        ; negative TTL
)

References

Detected automatically by VulnRadar. The check id is dns-soa-serial-stale, stable across every scan so you can filter or diff on it.

See every dns check

Questions

How severe is SOA Serial Looks Stale (Date-Based Convention)?
VulnRadar rates this info severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id dns-soa-serial-stale, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for soa serial looks stale (date-based convention)

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

SOA Serial Looks Stale (Date-Based Convention) | VulnRadar