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

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
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 199.34.228.67 does not match any cert SAN: pages-custom-19.weebly.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
TLS Certificate Expiry & Recommendations
47 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

47
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
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
DNS Records
1 A records, 38 ms lookup
PASS
1 A records, 38 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 199.34.228.67
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: cattailsenvironmental.com
Info::
2 nameserver(s) configured
Got: ns20.domaincontrol.com, ns19.domaincontrol.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 38 ms
Got: 38 ms
A199.34.228.67
AAAA—
CNAMEcattailsenvironmental.com
NSns20.domaincontrol.com, ns19.domaincontrol.com
MX
0 cattailsenvironmental-com.mail.protection.outlook.com
TXT
SPF v=spf1 include:secureserver.net -all
MS=ms14137640
CAALookup not available with standard resolver
Resolved in 38 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

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 54ms across 3 resolvers (spread 85ms)
PASS
Mean 54ms across 3 resolvers (spread 85ms)
Info::
Google: 26ms
Got: 26ms via 8.8.8.8:53
Info::
Cloudflare: 26ms
Got: 26ms via 1.1.1.1:53
Info::
Quad9: 111ms
Got: 111ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.cattailsenvironmental.com

https://www.cattailsenvironmental.com

24 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.cattailsenvironmental.com20024 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 18 URLs
PASS
robots.txt present, sitemap with 18 URLs
Info::
robots.txt is present
Got: 178 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 18 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 178 B Sitemaps referenced 1 User-agents NerdyBot, dotbot, * Blocking No — crawling allowed
Sitemap: https://www.cattailsenvironmental.com/sitemap.xml

User-agent: NerdyBot
Disallow: /

User-agent: dotbot
Crawl-delay: 10

User-agent: *
Disallow: /ajax/
Disallow: /apps/
sitemap.xml 200 OK
Type URL Set URLs 18 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::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.cattailsenvironmental.com/
301https://cattailsenvironmental.com/

Preferred variant: www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
cattailsenvironmental.com — via GoDaddy.com, LLC, 11 years, 4 months old, hosted on WEEBLY - Weebly, Inc., US
PASS
cattailsenvironmental.com — via GoDaddy.com, LLC, 11 years, 4 months old, hosted on WEEBLY - Weebly, Inc., US
Info::
Domain registered until May 9, 2030 (3 years, 9 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: GoDaddy.com, LLC
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: WEEBLY - Weebly, Inc., US
Got: AS27647
Domain expiry

1369 days

May 9, 2030

SSL certificate

47 days

Issued by Google Trust Services

Domain age

11 years, 4 months

Registered May 9, 2015

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WEEBLY - Weebly, Inc., US

ASN AS27647

199.34.228.67

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry 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 GoDaddy.com, LLC
Created May 9, 2015 (11 years, 4 months ago)
Expires May 9, 2030 (3 years, 9 months)
Last Updated May 9, 2025
Name Servers ns19.domaincontrol.com, ns20.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 199.34.228.67
ASN AS27647 (WEEBLY - Weebly, Inc., US)
Provider WEEBLY - Weebly, Inc., US
Data source: rdap (0.5s)

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 293 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
80 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
292 ms
Total Time Total request time from DNS lookup through full response.
294 ms

Connection waterfall

DNS Lookup 80 ms TCP Connect 1 ms TLS Handshake 11 ms Server Processing 200 ms Content Transfer 2 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: MAD)
Got: cf-ray: a26df7fa9ef1cc53-MAD
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: a26df7fa9ef1cc53-MAD
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=0, cf-cache-status=HIT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback