Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Sao Paulo, Brazil

403 Forbidden

Checks

6 PASS 10 REVIEW 1 FIX

Multi-Resolver DNS Speed

Action

Mean 203ms across 3 resolvers (spread 307ms)

FIX

Mean 203ms across 3 resolvers (spread 307ms)

Google: 2ms

Got: 2ms via 8.8.8.8:53

Quad9: 298ms

Got: 298ms via 9.9.9.9:53

Cloudflare: 309ms

Got: 309ms via 1.1.1.1:53

High latency spread between resolvers: 307ms (min 2ms / max 309ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 23.227.38.32 does not match any cert SAN: myshopify.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

No IPv6 (AAAA) records found

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

No IPv6 Support

About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

HTTP Probe Timing

Total 968 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

932 ms

TCP Connect

2 ms

TLS Handshake

23 ms

Time to First Byte

968 ms

Total Time

969 ms

Connection waterfall

DNS Lookup 932 ms TCP Connect 2 ms TLS Handshake 23 ms Server Processing 12 ms Content Transfer 0 ms

TLS Certificate Expiry & Recommendations

69 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

days left

0d 30d 60d 90d+

Recommended actions

Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
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

CDN & Delivery

Document on Cloudflare; assets also on Fastly, Bunny CDN

REVIEW

Document on Cloudflare; assets also on Fastly, Bunny CDN

Document is served via Cloudflare CDN (edge: GRU)

Got: cf-ray: a4c8bf32beeb02f2-GRU

Assets on Cloudflare: cdn.shopify.com (assets: 16), cache HIT

Got: cf-ray: a4c8c4befdbf019d-GRU

Assets on Fastly: static.klaviyo.com (assets: 11), cache HIT, HIT

Got: delegation klaviyo-onsite.map.fastly.net

Assets on Bunny CDN: fonts.bunny.net (assets: 4)

Got: delegation bunnyfonts.b-cdn.net

Assets on Cloudflare: instafeed.nfcube.com (assets: 4), cache HIT

Got: cf-ray: a4c8c4befbb8c075-GRU

Assets on Fastly: static-tracking.klaviyo.com (assets: 4), cache HIT, HIT

Got: delegation klaviyo-app.map.fastly.net

Assets on Cloudflare: static.joy.so (assets: 4), cache REVALIDATED

Got: cf-ray: a4c8c4befcd4d79f-GRU

Document served via CDN: Cloudflare

Provider Cloudflare Evidence cf-ray: a4c8bf32beeb02f2-GRU

Asset hosts on a CDN

cdn.shopify.com — Cloudflare · assets: 16 · Cache Status: HIT
static.klaviyo.com — Fastly · assets: 11 · Cache Status: HIT, HIT
fonts.bunny.net — Bunny CDN · assets: 4
instafeed.nfcube.com — Cloudflare · assets: 4 · Cache Status: HIT
static-tracking.klaviyo.com — Fastly · assets: 4 · Cache Status: HIT, HIT
static.joy.so — Cloudflare · assets: 4 · Cache Status: REVALIDATED

Other asset hosts

www.googletagmanager.com — assets: 4 · Google
connect.facebook.net — assets: 2 · below probe threshold
cdn.nfcube.com — assets: 1 · below probe threshold
scontent.cdninstagram.com — assets: 1 · below probe threshold
services.blend-ai.com — assets: 1 · below probe threshold
shop.app — assets: 1 · below probe threshold
static-wishlist.joy.so — assets: 1 · below probe threshold
www.gstatic.com — assets: 1 · below probe threshold

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

No CDN cache-status headers in the response

Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

DNS Records

1 A records, 1240 ms lookup

PASS

1 A records, 1240 ms lookup

Resolves to 1 IPv4 address(es)

Got: 23.227.38.32

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

3 nameserver(s) configured

Got: ns2.kudos.net.nz, ns1.kudos.net.nz, ns3.kudos.net.nz

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (1240 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 1240 ms

A	23.227.38.32
AAAA	—
CNAME	—
NS	ns2.kudos.net.nz, ns1.kudos.net.nz, ns3.kudos.net.nz
MX	10 mx.raptonline.co.nz.cust.b.hostedemail.com
TXT	SPF v=spf1 a mx include:_spf.hostedemail.com include:boltmail.co.nz ~all klaviyo-site-verification=YmfRJZ
CAA	Lookup not available with standard resolver

Resolved in 1240 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Redirect Chain

0 redirect(s), 332 ms total

PASS

0 redirect(s), 332 ms total

https://raptonline.co.nz

332 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://raptonline.co.nz	403	332 ms	HTTP/1.1	cloudflare

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

403https://www.raptonline.co.nz/

200https://raptonline.co.nz/

HTTP → HTTPS

301http://raptonline.co.nz/ → https://raptonline.co.nz/

Consistent

A+

Domain Intelligence

raptonline.co.nz — via Kudos Solutions Limited, 19 years, 7 months old, hosted on Cloudflare

PASS

raptonline.co.nz — via Kudos Solutions Limited, 19 years, 7 months old, hosted on Cloudflare

Registrar: Kudos Solutions Limited

Registrar lock is NOT enabled

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.

Hosting: Cloudflare

Got: AS13335

Domain expiry

Unknown

SSL certificate

69 days

Issued by Let's Encrypt

Domain age

19 years, 7 months

Registered June 5, 2007

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

23.227.38.32

Registrar

Kudos Solutions Limited

Unlocked 3 NS records

Expiry timeline

Today

+1 year

SSL expiry Danger zone (≤30 days)

Recommended actions

Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Kudos Solutions Limited

Created June 5, 2007 (19 years, 7 months ago)

Last Updated July 20, 2026

Name Servers ns1.kudos.net.nz, ns2.kudos.net.nz, ns3.kudos.net.nz

Hosting

IP Address 23.227.38.32

ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)

Provider Cloudflare

Data source: whois (2.9s)

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.

Why this matters

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

A+

Health Check Endpoint

Health endpoint at https://raptonline.co.nz/healthz (HTTP 200)

PASS

Health endpoint at https://raptonline.co.nz/healthz (HTTP 200)

Public health endpoint at https://raptonline.co.nz/healthz

Got: https://raptonline.co.nz/healthz

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.