Skip to content
https://www.randaroofing.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
12
PASS
5
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
17
5 PASS 12 REVIEW
B
DNS Records
2 A records, 27 ms lookup
REVIEW
2 A records, 27 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.3.8, 162.159.143.12
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: cdn3.wixdns.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 27 ms
Got: 27 ms
A172.66.3.8, 162.159.143.12
AAAA—
CNAMEcdn3.wixdns.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 27 ms

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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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.
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 172.66.3.8: lookup 172.66.3.8: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 162.159.143.12: lookup 162.159.143.12: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
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.

B
Domain Intelligence
randaroofing.com — via Wix.com Ltd., 6 years old, hosted on wix_com - Wix.com Ltd., IL
REVIEW
randaroofing.com — via Wix.com Ltd., 6 years old, hosted on wix_com - Wix.com Ltd., IL
Critical::
Domain expires in 16 days
This domain expires on October 29, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires Oct 29, 2026
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: Wix.com 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: wix_com - Wix.com Ltd., IL
Got: AS58182
Domain expiry

10 days

October 29, 2026

SSL certificate

52 days

Issued by Google Trust Services

Domain age

6 years

Registered October 29, 2020

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

wix_com - Wix.com Ltd., IL

ASN AS58182

185.230.63.186

Registrar

Wix.com Ltd.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Wix.com Ltd.
Created October 29, 2020 (6 years ago)
Expires October 29, 2026 (16 days)
Last Updated November 27, 2025
Name Servers ns14.wixdns.net, ns15.wixdns.net
DNSSEC Not enabled
Hosting
IP Address 185.230.63.186
ASN AS58182 (wix_com - Wix.com Ltd., IL)
Provider wix_com - Wix.com Ltd., IL
Data source: rdap (0.3s)

This domain expires on October 29, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Certificate validity

52
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 & Delivery
Document on Cloudflare; assets also on AWS CloudFront, Google Cloud CDN
REVIEW
Document on Cloudflare; assets also on AWS CloudFront, Google Cloud CDN
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a497f4476df0700c-CDG
Info::
Assets on AWS CloudFront: static.wixstatic.com (assets: 41), cache Hit from cloudfront
Got: delegation d1cq301dpr7fww.cloudfront.net
Info::
Assets on Google Cloud CDN: static.parastorage.com (assets: 27), cache miss
Got: via: 1.1 varnish (Varnish/6.0),1.1 varnish (Varnish/6.0), 1.1 google
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a497f4476df0700c-CDG

Asset hosts on a CDN

  • static.wixstatic.com — AWS CloudFront · assets: 41 · Cache Status: Hit from cloudfront
  • static.parastorage.com — Google Cloud CDN · assets: 27 · Cache Status: miss

Other asset hosts

  • browser.sentry-cdn.com — assets: 2 · below probe threshold
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+
Multi-Resolver DNS Speed
Mean 21ms across 3 resolvers (spread 26ms)
PASS
Mean 21ms across 3 resolvers (spread 26ms)
Info::
Quad9: 5ms
Got: 5ms via 9.9.9.9:53
Info::
Google: 29ms
Got: 29ms via 8.8.8.8:53
Info::
Cloudflare: 31ms
Got: 31ms via 1.1.1.1:53
A+
Redirect Chain
0 redirect(s), 62 ms total
PASS
0 redirect(s), 62 ms total

https://www.randaroofing.com

62 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.randaroofing.com40362 msHTTP/1.1cloudflare
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.randaroofing.com/
301https://randaroofing.com/

Preferred variant: www

HTTP → HTTPS

301http://www.randaroofing.com/ → https://www.randaroofing.com/

Consistent

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

Connection waterfall

DNS Lookup 138 ms TCP Connect 17 ms TLS Handshake 27 ms Server Processing 21 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback