Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
# robots.txt is set in Fastly; this is a copy for reference
User-agent: *
Disallow: /admin/
Sitemap: https://www.rnz.co.nz/sitemap/sitemap.xml.gz
Crawl-delay: 7
# Direct the most annoying crawlers not to index
User-agent: psbot
Disallow: /
User-agent: magpie-crawler
Disallow: /
User-agent: turnitinbot
Disallow: /
# Block AI bots
User-Agent: *
Allow: /
User-Agent: AdsBot-Google
Disallow: /
User-Agent: Amazonbot
Disallow: /
User-Agent: anthropic-ai
Disallow: /
User-Agent: Applebot-Extended
Disallow: /
User-Agent: Bytespider
Disallow: /
User-Agent: CCBot
Disallow: /
User-Agent: ChatGPT-User
Disallow: /
User-Agent: ClaudeBot
Disallow: /
User-Agent: Claude-SearchBot
Disallow: /
User-Agent: Claude-Web
Disallow: /
User-Agent: cohere-ai
Disallow: /
User-Agent: Diffbot
Disallow: /
User-Agent: DuckAssistBot
Disallow: /
User-Agent: FriendlyCrawler
Disallow: /
User-Agent: Gemini-Deep-Research
Disallow: /
User-Agent: Google-CloudVertexBot
Disallow: /
User-Agent: Google-Extended
Disallow: /
User-Agent: GoogleOther
Disallow: /
User-Agent: GPTBot
Disallow: /
User-Agent: ICC-Crawler
Disallow: /
User-Agent: img2dataset
Disallow: /
User-Agent: MistralAI-User
Disallow: /
User-Agent: OAI-SearchBot
Disallow: /
User-Agent: omgili
Disallow: /
User-Agent: omgilibot
Disallow: /
User-Agent: peer39_crawler
Disallow: /
User-Agent: peer39_crawler/1.0
Disallow: /
User-Agent: PerplexityBot
Disallow: /
User-Agent: Perplexity-User
Disallow: /
User-Agent: Webz.io
Disallow: /
User-Agent: YouBot
Disallow: /
User-Agent: facebookexternalhit
Allow: /
# Slow down the high-download / low-return crawlers
User-agent: bingbot
User-agent: msnbot
User-agent: Yandex
Crawl-delay: 20
User-agent: Wget
Crawl-delay: 10
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations87 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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 Records4 A records, 7 ms lookupPASS
| A | 151.101.130.133, 151.101.194.133, 151.101.66.133, 151.101.2.133 |
| AAAA | 2a04:4e42::645, 2a04:4e42:400::645, 2a04:4e42:600::645, 2a04:4e42:200::645 |
| CNAME | — |
| NS | ns-1117.awsdns-11.org, ns-1948.awsdns-51.co.uk, ns-262.awsdns-32.com, ns-646.awsdns-16.net |
| MX | 0 rnz-co-nz.mail.protection.outlook.com |
| TXT | 0439a510808349c1a78ec07dab2d8f13 MS=ms79391666 apple-domain-verification=aY3Pc1yjFfNSgPko ed0d36face9f4c75969761621e2bb693 facebook-domain-verification=y6p874gox8iq1pk5b775tbsmblyxxy google-site-verification=RjtXTa8k63fFxtOnGuVvl82TrsGlMFw-CE7GTMXemZo mandrill_verify.irqSkCn_9GTZVbZuaIgibQ smartsheet-site-validation=6lhIJoP5nVvgpNDpmm_l7rauojVxzMhM SPF v=spf1 include:spf.protection.outlook.com include:spf.mandrillapp.com include:_s... ydXeepFbcmKNLqTiTJgnetMxeh2mpBMVWq4D+CNeSBtc9H8xlVqGVcYtX16wCtrKFKjzA9xkwp8HNfAW... |
| 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), 27 ms totalPASS
https://rnz.co.nz
14 ms · HTTP/1.1
https://www.rnz.co.nz/
12 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://rnz.co.nz | 301 | 14 ms | HTTP/1.1 | Varnish |
| 2 | https://www.rnz.co.nz/ | 200 | 12 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Domain Intelligencernz.co.nz — via Metaname, 29 years, 6 months oldPASS
Unknown
87 days
Issued by Let's Encrypt
29 years, 6 months
Registered February 26, 1997
Status unknown
Protects against DNS spoofing
Unknown
2a04:4e42:600::645
Metaname
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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