Domain last updated date
When the registry record last changed — a nameserver move, a renewal or a transfer.
The date the registry record last changed. Typical reasons are a renewal, a change of nameservers, an edit of the contact data, a status change such as setting or removing the transfer lock, or a transfer to another registrar. At some registries even an automatic renewal moves the date, so a recent value is often routine.
Why it is worth a look:
- Unexpected changes. If nobody on your side touched the domain but the date is from yesterday, check at once what changed: the nameservers, the registrar, the status codes. A domain hijack begins exactly with an edit of the record.
- Troubleshooting DNS. After a nameserver move this date confirms the registry has accepted the change; propagation in resolvers still takes up to the old NS records' TTL.
- Due diligence. A domain bought recently usually shows a transfer or a change of contacts here.
What the row shows
The date comes from RDAP or WHOIS and is informational. Not every registry publishes it; when it does not, the row is simply not shown.
How to protect the record
Keep the transfer lock on, enable two-factor sign-in at the registrar, and make sure change notices reach a mailbox that someone reads. Compare the date with the registry status when something looks wrong.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Domain registration”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data