Skip to content
https://rjwdigital.com.au

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
7 PASS 8 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 287ms across 3 resolvers (spread 380ms)
FIX
Mean 287ms across 3 resolvers (spread 380ms)
Info::
Google: 157ms
Got: 157ms via 8.8.8.8:53
Info::
Quad9: 168ms
Got: 168ms via 9.9.9.9:53
Info::
Cloudflare: 537ms
Got: 537ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 380ms (min 157ms / max 537ms)
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
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 34.237.47.210 does not match any cert SAN: ec2-34-237-47-210.compute-1.amazonaws.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.
B
Redirect Chain
1 redirect(s), 1078 ms total
REVIEW
1 redirect(s), 1078 ms total
Info::
Single redirect
Got: https://rjwdigital.com.au → https://www.rjwdigital.com.au (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1078 ms total
Got: 1078 ms

https://rjwdigital.com.au

303 ms · HTTP/1.1

301

https://www.rjwdigital.com.au

775 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rjwdigital.com.au301303 msHTTP/1.1nginx
2https://www.rjwdigital.com.au200775 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.rjwdigital.com.au/
200https://rjwdigital.com.au/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://rjwdigital.com.au/ https://rjwdigital.com.au/

Consistent

B
TLS Certificate Expiry & Recommendations
36 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
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.
A
DNS Records
1 A records, 299 ms lookup
PASS
1 A records, 299 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.237.47.210
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns2.nameserver.net.au, ns1.nameserver.net.au, ns3.nameserver.net.au
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (299 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 299 ms
A34.237.47.210
AAAA
CNAME
NSns2.nameserver.net.au, ns1.nameserver.net.au, ns3.nameserver.net.au
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
google-site-verification=y2oewhoxb5upbs70iwfu9gnianfaq5bo-k9fzzzbskw
brevo-code:2921f2c3366b87c7c5919ac9ee5fdb76
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 299 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
Info::
No CNAME record present
A+
Crawlability
robots.txt present, sitemap with 72 URLs
PASS
robots.txt present, sitemap with 72 URLs
Info::
robots.txt is present
Got: 25 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 72 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 25 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: * 
Disallow:

A+
Domain Intelligence
rjwdigital.com.au — via Synergy Wholesale Accreditations Pty Ltd, hosted on AWS
PASS
rjwdigital.com.au — via Synergy Wholesale Accreditations Pty Ltd, hosted on AWS
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: AWS
Got: AS14618
Domain expiry

Unknown

SSL certificate

36 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

34.237.47.210

Registrar

Synergy Wholesale Accreditations Pty Ltd

Unlocked 3 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 30, 2025
Name Servers ns1.nameserver.net.au, ns2.nameserver.net.au, ns3.nameserver.net.au
DNSSEC Not enabled
Hosting
IP Address 34.237.47.210
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.6s)

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

A
HTTP Probe Timing
Total 623 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
311 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
98 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
109 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
623 ms
Total Time Total request time from DNS lookup through full response.
624 ms

Connection waterfall

DNS Lookup 311 ms TCP Connect 98 ms TLS Handshake 109 ms Server Processing 106 ms Content Transfer 0 ms
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 3 header(s)
Got: age=602067, x-cache=HIT, x-cache-hits=138
A+
Health Check Endpoint
Health endpoint at https://rjwdigital.com.au/health (HTTP 200)
PASS
Health endpoint at https://rjwdigital.com.au/health (HTTP 200)
Info::
Public health endpoint at https://rjwdigital.com.au/health
Got: https://rjwdigital.com.au/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback