Skip to content
https://gar-bau.ro

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
17
7 PASS 10 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.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 216.198.79.1: lookup 216.198.79.1: 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
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 redirects to HTTPS permanently
Got: HTTP 308

www / non-www

200https://www.gar-bau.ro/
200https://gar-bau.ro/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://gar-bau.ro/ → https://gar-bau.ro/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
Vercel
REVIEW
Vercel
Info::
Document is served via Vercel CDN
Got: x-vercel-id: cdg1::rvd86-1793103724141-559fe4d12f18
Document served via CDN: Vercel
Provider Vercel Evidence x-vercel-id: cdg1::rvd86-1793103724141-559fe4d12f18
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+
DNS Records
1 A records, 75 ms lookup
PASS
1 A records, 75 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 216.198.79.1
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: jewel.ns.cloudflare.com, jimmy.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 75 ms
Got: 75 ms
A216.198.79.1
AAAA—
CNAME—
NSjewel.ns.cloudflare.com, jimmy.ns.cloudflare.com
MX
10 mx.hitter.ro
TXT
yahoo-verification-key=VgSRtdxXkOsBUWW4RNOe/O7ZiDzTYearfHjorJSD0Ig=
SPF v=spf1 mx a ~all
CAALookup not available with standard resolver
Resolved in 75 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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Multi-Resolver DNS Speed
Mean 50ms across 3 resolvers (spread 81ms)
PASS
Mean 50ms across 3 resolvers (spread 81ms)
Info::
Cloudflare: 22ms
Got: 22ms via 1.1.1.1:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Quad9: 103ms
Got: 103ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 402 ms total
PASS
1 redirect(s), 402 ms total
Info::
Single redirect
Got: https://gar-bau.ro → https://www.gar-bau.ro/ (308)
Info::
WWW normalization redirect

https://gar-bau.ro

107 ms · HTTP/1.1

308

https://www.gar-bau.ro/

296 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gar-bau.ro308107 msHTTP/1.1Vercel
2https://www.gar-bau.ro/200296 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 127 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 127 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /admin
Disallow: /api

Host: http://localhost:3000
Sitemap: http://localhost:3000/sitemap.xml

A+
Domain Intelligence
gar-bau.ro — via Claus Web SRL, 20 years, 11 months old, hosted on AWS
PASS
gar-bau.ro — via Claus Web SRL, 20 years, 11 months old, hosted on AWS
Info::
Registrar: Claus Web SRL
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: AS16509
Domain expiry

Unknown

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

20 years, 11 months

Registered February 24, 2006

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

216.198.79.1

Registrar

Claus Web SRL

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Claus Web SRL
Created February 24, 2006 (20 years, 11 months ago)
Name Servers jewel.ns.cloudflare.com, jimmy.ns.cloudflare.com
Hosting
IP Address 216.198.79.1
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (0.8s)

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

Connection waterfall

DNS Lookup 38 ms TCP Connect 1 ms TLS Handshake 113 ms Server Processing 29 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