Skip to content
https://robuta.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
6
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 6 REVIEW 1 FIX
D
Multi-Resolver DNS Speed
Action
Mean 383ms across 3 resolvers (spread 977ms)
FIX
Mean 383ms across 3 resolvers (spread 977ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 134ms
Got: 134ms via 1.1.1.1:53
Info::
Quad9: 997ms
Got: 997ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 977ms (min 20ms / max 997ms)
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.
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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 162.159.140.164: lookup 162.159.140.164: 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 172.66.0.162: lookup 172.66.0.162: 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 2606:4700:7::a2: lookup 2606:4700:7::a2: 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 2a06:98c1:58::a2: lookup 2a06:98c1:58::a2: 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.
B
TLS Certificate Expiry & Recommendations
81 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

81
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
2 A records, 99 ms lookup
PASS
2 A records, 99 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 162.159.140.164, 172.66.0.162
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:7::a2, 2a06:98c1:58::a2
Info::
3 nameserver(s) configured
Got: ns2.digitalocean.com, ns1.digitalocean.com, ns3.digitalocean.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 99 ms
Got: 99 ms
A162.159.140.164, 172.66.0.162
AAAA2606:4700:7::a2, 2a06:98c1:58::a2
CNAME—
NSns2.digitalocean.com, ns1.digitalocean.com, ns3.digitalocean.com
MX
10 mx1.privateemail.com
10 mx2.privateemail.com
TXT
pinterest-site-verification=64edb918392a0594f3ee39ea4a644c64
SPF v=spf1 include:spf.privateemail.com ~all
google-site-verification=PTMMbxYnCxxZiFB0PJg1VOwmBC124rRn-FDZe56cvEg
CAALookup not available with standard resolver
Resolved in 99 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://robuta.com

https://robuta.com

233 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://robuta.com200233 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:7::a2, 2a06:98c1:58::a2
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:7::a2, 2a06:98c1:58::a2 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 52 URLs
PASS
robots.txt present, sitemap with 52 URLs
Info::
robots.txt is present
Got: 86 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 52 entries
Info::
Sitemap index with 52 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 86 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://robuta.com/static/sitemaps/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 52 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::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.robuta.com/
200https://robuta.com/

HTTP → HTTPS

301http://robuta.com/ → https://robuta.com/

Consistent

A+
Domain Intelligence
robuta.com — via NameCheap, Inc., 7 years, 1 months old
PASS
robuta.com — via NameCheap, Inc., 7 years, 1 months old
Info::
Domain registered until Jul 12, 2027 (1 years 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: NameCheap, 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

365 days

July 12, 2027

SSL certificate

81 days

Issued by Let's Encrypt

Domain age

7 years, 1 months

Registered July 12, 2019

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:7::a2

Registrar

NameCheap, Inc.

Unlocked 3 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 NameCheap, Inc.
Created July 12, 2019 (7 years, 1 months ago)
Expires July 12, 2027 (1 years)
Last Updated June 12, 2026
Name Servers ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:7::a2
Data source: rdap (0.2s)

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 593 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
2 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.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
593 ms
Total Time Total request time from DNS lookup through full response.
593 ms

Connection waterfall

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

Send Feedback