Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations72 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records2 A records, 18 ms lookupPASS
| A | 162.159.141.224, 172.66.1.220 |
| AAAA | 2a06:98c1:58::1d8, 2606:4700:7::1d8 |
| CNAME | — |
| NS | blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | MS=ms73365380 adobe-idp-site-verification=4d443bb146b2a60fc0c0216c899a6ef9baa971cc3c36ac4b3020... airtable-verification=7f23bd05102c5a2c073b0d0689ecaf71 atlassian-domain-verification=uUTQHYge655RxaiCqp-IAyc/Q7GgtoJziDouyp0rB7n8OUdp4q... cursor-domain-verification-9kj3cx=DlgqFQBoElq0vaCCvAoYXQgau docusign=ea9c05c4-b519-4641-a503-101c5e1fa11f facebook-domain-verification=un5j5b6521kv0gxa930ok06i04iz1h facebook-domain-verification=w9nv51lpzdtxwj37upprvtwk3yupdc google-site-verification=6Xt2j4qA0zw4f2-J0ixz5iZKXooj9pV1GCBcWzKMBIQ google-site-verification=pxcshjVSyXUOR8V-XLmAY87XteFHBRss372hYJDSMMw google-site-verification=zftV3TPQfrHbRtEFYSqpGJDJ8sejzZTB-7XE69upLks knowbe4-site-verification=fa92b9e4fa2fbe928824de444cebea5e openai-domain-verification=dv-efHPfN1Kg8RIqgEEQdklkCdR shopify-verification-code=JUTSjHX4FqRaBTRHi2clc9PTsDQzvY slack-domain-verification=dhsNgn8293A7XDeCeXUkZ3Zb9j3wbw5C3wjQ6TXL SPF v=spf1 include:mail.zendesk.com ip4:64.125.213.247 ip4:216.223.13.247 include:_s... windsurf-verification=dpvN4Mj8Kmbfgxsum_Y5SQfktphHotCcZAFa9tJd-7U= |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 642 ms totalPASS
https://byrdie.com
419 ms · HTTP/1.1
https://www.byrdie.com/
224 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://byrdie.com | 301 | 419 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.byrdie.com/ | 200 | 224 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 1 URLsPASS
User-agent: *
Disallow: *.pdf
Disallow: /embed?
User-agent: Pinterest
Disallow:
User-agent: Pinterestbot
Disallow:
User-agent: CCBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /thmb/
User-agent: OAI-SearchBot
Disallow: /thmb/
User-agent: GPTBot
Disallow: /thmb/
User-agent: news-please
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: cohere-ai
Disallow: /
User-agent: ImagesiftBot
Disallow: /
User-agent: FriendlyCrawler
Disallow: /
User-agent: Quora-Bot
Disallow: /
User-agent: omgilibot
Disallow: /
User-agent: omgili
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: Perplexity-User
Disallow: /
User-agent: Google-Extended
Disallow: /
Sitemap: https://www.byrdie.com/sitemap.xml
Sitemap: https://www.byrdie.com/google-news-sitemap.xml
A+Domain Intelligencebyrdie.com — via MarkMonitor Inc., 18 years, 7 months oldPASS
163 days
December 23, 2026
72 days
Issued by Let's Encrypt
18 years, 7 months
Registered December 23, 2007
Not enabled
Protects against DNS spoofing
Unknown
2a06:98c1:58::1d8
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice