Skip to content
http://www.ricksmainroofing.com

Infrastructure

· 16 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
7
PASS
8
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
16
8 PASS 7 REVIEW 1 FIX
D
Redirect Chain
Action
2 redirect(s), 1687 ms total
FIX
2 redirect(s), 1687 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from http://www.ricksmainroofing.com to https://ricksmainroofing.com/
Warning::
Redirect overhead: 1687 ms total
Got: 1687 ms

http://www.ricksmainroofing.com

46 ms · HTTP/1.1

301

https://www.ricksmainroofing.com/

310 ms · HTTP/1.1

301

https://ricksmainroofing.com/

1331 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1http://www.ricksmainroofing.com30146 msHTTP/1.1cloudflare
2https://www.ricksmainroofing.com/301310 msHTTP/1.1cloudflare
3https://ricksmainroofing.com/2001331 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from http://www.ricksmainroofing.com to https://ricksmainroofing.com/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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
4 PTR record(s) found (no cert data to match against)
REVIEW
4 PTR record(s) found (no cert data to match against)
Info::
PTR lookup failed for 172.67.184.29: lookup 172.67.184.29: no such host
Info::
PTR lookup failed for 104.21.68.6: lookup 104.21.68.6: no such host
Info::
PTR lookup failed for 2606:4700:3030::6815:4406: lookup 2606:4700:3030::6815:4406: no such host
Info::
PTR lookup failed for 2606:4700:3037::ac43:b81d: lookup 2606:4700:3037::ac43:b81d: no such host
B
CDN & Delivery
Document on Cloudflare; assets also on AWS CloudFront
REVIEW
Document on Cloudflare; assets also on AWS CloudFront
Info::
Document is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: a4b8e045af4cc475-EWR
Info::
Assets on AWS CloudFront: cdn.trustindex.io (assets: 40), cache Hit from cloudfront
Got: delegation dhtt2nmvztmk3.cloudfront.net
Info::
Assets on Cloudflare: ricksmainroofing.com (assets: 10)
Got: cf-ray: a4b8e402fb3c43a3-EWR
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a4b8e045af4cc475-EWR

Asset hosts on a CDN

  • cdn.trustindex.io — AWS CloudFront · assets: 40 · Cache Status: Hit from cloudfront
  • ricksmainroofing.com — Cloudflare · assets: 10

Other asset hosts

  • lh3.googleusercontent.com — assets: 8 · Google
  • static.cloudflareinsights.com — assets: 1 · 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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
2 A records, 16 ms lookup
PASS
2 A records, 16 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.184.29, 104.21.68.6
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3030::6815:4406, 2606:4700:3037::ac43:b81d
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: 16 ms
Got: 16 ms
A172.67.184.29, 104.21.68.6
AAAA2606:4700:3030::6815:4406, 2606:4700:3037::ac43:b81d
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 16 ms

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)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 22ms across 3 resolvers (spread 31ms)
PASS
Mean 22ms across 3 resolvers (spread 31ms)
Info::
Cloudflare: 11ms
Got: 11ms via 1.1.1.1:53
Info::
Google: 14ms
Got: 14ms via 8.8.8.8:53
Info::
Quad9: 42ms
Got: 42ms via 9.9.9.9:53
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3030::6815:4406, 2606:4700:3037::ac43:b81d
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:3030::6815:4406, 2606:4700:3037::ac43:b81d Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 104 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 104 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: 

Disallow: /cgi-bin/

Sitemap: https://ricksmainroofing.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 2 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)

www / non-www

200http://www.ricksmainroofing.com/
301http://ricksmainroofing.com/

Preferred variant: www

A+
Domain Intelligence
ricksmainroofing.com — via Cloudflare, Inc., 23 years, 5 months old
PASS
ricksmainroofing.com — via Cloudflare, Inc., 23 years, 5 months old
Info::
Domain registered until Aug 29, 2027 (10 months remaining)
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: Cloudflare, Inc.
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.
Domain expiry

314 days

August 29, 2027

SSL certificate

No certificate data

Domain age

23 years, 5 months

Registered August 29, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3030::6815:4406

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain 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 Cloudflare, Inc.
Created August 29, 2003 (23 years, 5 months ago)
Expires August 29, 2027 (10 months)
Last Updated July 30, 2026
Name Servers ingrid.ns.cloudflare.com, norman.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3030::6815:4406
Data source: rdap (0.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

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

Connection waterfall

DNS Lookup 22 ms TCP Connect 2 ms TLS Handshake 0 ms Server Processing 41 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback