Skip to content
https://techguys.nz

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
10
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
5 PASS 10 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 165ms across 3 resolvers (spread 331ms)
FIX
Mean 165ms across 3 resolvers (spread 331ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Quad9: 125ms
Got: 125ms via 9.9.9.9:53
Info::
Cloudflare: 351ms
Got: 351ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 331ms (min 20ms / max 351ms)
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.
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
1 A records, 25 ms lookup
REVIEW
1 A records, 25 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 35.244.103.1
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: thetechguysltdnz.odoo.com
Info::
No NS records found
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 25 ms
Got: 25 ms
A35.244.103.1
AAAA—
CNAMEthetechguysltdnz.odoo.com
NS—
MX
10 au15a.odoo.com
TXT
SPF v=spf1 include:_spf.odoo.com -all
CAALookup not available with standard resolver
Resolved in 25 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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
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).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 35.244.103.1 does not match any cert SAN: 1.103.244.35.bc.googleusercontent.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.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
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

B
HTTP Probe Timing
Total 1130 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
157 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
319 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
322 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.13 s
Total Time Total request time from DNS lookup through full response.
1.13 s

Connection waterfall

DNS Lookup 157 ms TCP Connect 319 ms TLS Handshake 322 ms Server Processing 332 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
41 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

41
days left
0d 30d 60d 90d+

Recommended actions

  • 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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
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.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.techguys.nz

https://www.techguys.nz

959 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.techguys.nz200959 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 5 URLs
PASS
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 110 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 110 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed


User-agent: *
Sitemap: https://www.techguys.nz/sitemap.xml


##############
#   custom   #
##############
sitemap.xml 200 OK
Type URL Set URLs 5 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.techguys.nz/
https://techguys.nz/

HTTP → HTTPS

301http://www.techguys.nz/ → https://www.techguys.nz/

Consistent

A+
Domain Intelligence
techguys.nz — via 1st Domains Limited, 8 years, 4 months old, hosted on VOYAGERNET-AS-AP Voyager Internet Ltd., NZ
PASS
techguys.nz — via 1st Domains Limited, 8 years, 4 months old, hosted on VOYAGERNET-AS-AP Voyager Internet Ltd., NZ
Info::
Registrar: 1st Domains Limited
Warning::
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.
Info::
Hosting: VOYAGERNET-AS-AP Voyager Internet Ltd., NZ
Got: AS56030
Domain expiry

Unknown

SSL certificate

41 days

Issued by Let's Encrypt

Domain age

8 years, 4 months

Registered January 28, 2018

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

VOYAGERNET-AS-AP Voyager Internet Ltd., NZ

ASN AS56030

210.55.30.67

Registrar

1st Domains Limited

Unlocked 2 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 1st Domains Limited
Created January 28, 2018 (8 years, 4 months ago)
Last Updated January 2, 2026
Name Servers ns1.1stdomains.net.nz, ns2.1stdomains.net.nz
Hosting
IP Address 210.55.30.67
ASN AS56030 (VOYAGERNET-AS-AP Voyager Internet Ltd., NZ)
Provider VOYAGERNET-AS-AP Voyager Internet Ltd., NZ
Data source: whois (1.4s)

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

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

Send Feedback