Skip to content
https://www.newlivingdesigns.com.au

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
3
REVIEW
9
PASS
5
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
17
5 PASS 9 REVIEW 3 FIX
D
Multi-Resolver DNS Speed
Action
Mean 167ms across 3 resolvers (spread 329ms)
FIX
Mean 167ms across 3 resolvers (spread 329ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Google: 170ms
Got: 170ms via 8.8.8.8:53
Info::
Quad9: 331ms
Got: 331ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 329ms (min 2ms / max 331ms)
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.
F
HTTP Probe Timing
Action
Total 4366 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
582 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
409 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
414 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
4.36 s
Total Time Total request time from DNS lookup through full response.
4.37 s

Connection waterfall

DNS Lookup 582 ms TCP Connect 409 ms TLS Handshake 414 ms Server Processing 2.96 s Content Transfer 2 ms
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

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

B
DNS Records
1 A records, 1134 ms lookup
REVIEW
1 A records, 1134 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 110.232.143.16
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: newlivingdesigns.com.au
Info::
2 nameserver(s) configured
Got: ns2.syd6.hostingplatform.net.au, ns1.syd6.hostingplatform.net.au
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (1134 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1134 ms
A110.232.143.16
AAAA—
CNAMEnewlivingdesigns.com.au
NSns2.syd6.hostingplatform.net.au, ns1.syd6.hostingplatform.net.au
MX
0 newlivingdesigns-com-au.mail.protection.outlook.com
TXT
SPF v=spf1 include:_spf.mlsend.com include:spf.protection.outlook.com -all
SPF v=spf1 include:spf.protection.outlook.com -all
MS=ms10620510
google-site-verification=fCCXLxE4R2k6acM_C80ZcyX6ZtxQTZx2yFN7aPHJBc0
CAALookup not available with standard resolver
Resolved in 1134 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

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

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 110.232.143.16 does not match any cert SAN: s04dd.syd6.hostingplatform.net.au
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
TLS Certificate Expiry & Recommendations
70 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

70
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
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.newlivingdesigns.com.au

https://www.newlivingdesigns.com.au

1738 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.newlivingdesigns.com.au2001738 msHTTP/1.1LiteSpeed
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 170 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 170 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /*?*

Disallow: /*/feed/

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php


Sitemap: https://www.newlivingdesigns.com.au/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.newlivingdesigns.com.au/
301https://newlivingdesigns.com.au/

Preferred variant: www

HTTP → HTTPS

301http://www.newlivingdesigns.com.au/ → https://www.newlivingdesigns.com.au/

Consistent

A+
Domain Intelligence
newlivingdesigns.com.au — via Synergy Wholesale Accreditations Pty Ltd, hosted on SYNERGYWHOLESALE-AP SYNERGY WHOLESALE PTY LTD, AU
PASS
newlivingdesigns.com.au — via Synergy Wholesale Accreditations Pty Ltd, hosted on SYNERGYWHOLESALE-AP SYNERGY WHOLESALE PTY LTD, AU
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Synergy Wholesale Accreditations Pty Ltd
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: SYNERGYWHOLESALE-AP SYNERGY WHOLESALE PTY LTD, AU
Got: AS45638
Domain expiry

Unknown

SSL certificate

70 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SYNERGYWHOLESALE-AP SYNERGY WHOLESALE PTY LTD, AU

ASN AS45638

110.232.143.16

Registrar

Synergy Wholesale Accreditations Pty Ltd

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Synergy Wholesale Accreditations Pty Ltd
Last Updated August 15, 2026
Name Servers ns1.syd6.hostingplatform.net.au, ns2.syd6.hostingplatform.net.au
DNSSEC Not enabled
Hosting
IP Address 110.232.143.16
ASN AS45638 (SYNERGYWHOLESALE-AP SYNERGY WHOLESALE PTY LTD, AU)
Provider SYNERGYWHOLESALE-AP SYNERGY WHOLESALE PTY LTD, AU
Data source: rdap (2.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

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