Skip to content
https://rodizio.ro

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
11
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
6 PASS 11 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 185.248.197.90 does not match any cert SAN: fortza.net
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.
B
Multi-Resolver DNS Speed
Mean 135ms across 3 resolvers (spread 79ms)
REVIEW
Mean 135ms across 3 resolvers (spread 79ms)
Info::
Google: 95ms
Got: 95ms via 8.8.8.8:53
Info::
Quad9: 136ms
Got: 136ms via 9.9.9.9:53
Info::
Cloudflare: 174ms
Got: 174ms via 1.1.1.1:53
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::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

500https://www.rodizio.ro/
200https://rodizio.ro/

HTTP → HTTPS

200http://rodizio.ro/

HTTP version does not redirect to HTTPS

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

Certificate validity

60
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
C
CDN & Delivery
Action
Assets on Cloudflare (host pxgcdn.com, 5 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host pxgcdn.com, 5 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (pxgcdn.com, 5 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a4efcdc93e18c627-CDG
Info::
Assets on Cloudflare: pxgcdn.com (assets: 5), cache HIT
Got: cf-ray: a4efcdc93e18c627-CDG
Info::
Assets on Cloudflare: cdnjs.cloudflare.com (assets: 4), cache BYPASS
Got: cf-ray: a4efcdc93f75d12e-CDG
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • pxgcdn.com — Cloudflare · assets: 5 · Cache Status: HIT
  • cdnjs.cloudflare.com — Cloudflare · assets: 4 · Cache Status: BYPASS

Other asset hosts

  • connect.facebook.net — assets: 2 · below probe threshold
  • fonts.googleapis.com — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 2 · below probe threshold
  • ajax.googleapis.com — assets: 1 · below probe threshold
  • www.google-analytics.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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: 500, /health: 500, /healthz: 500, /ping: 500, /status: 500.
A+
DNS Records
1 A records, 84 ms lookup
PASS
1 A records, 84 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.248.197.90
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: ns2.fortza.net, ns1.fortza.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 84 ms
Got: 84 ms
A185.248.197.90
AAAA—
CNAME—
NSns2.fortza.net, ns1.fortza.net
MX
1 rodizio.ro
TXT
SPF v=spf1 ip4:185.248.197.0 ip4:185.248.197.90 ip4:185.248.196.2 ip4:185.248.196.12...
google-site-verification=bA99WCaoXDyAtKHiOwtXxMcElDBJHsuhYCU0YHlTD4A
google-site-verification=RsYaT__ux-SNqoQtJUpApWcNmO6HJ5Lw4DCH-I9dhoQ
CAALookup not available with standard resolver
Resolved in 84 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://rodizio.ro

https://rodizio.ro

178 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rodizio.ro200178 msHTTP/1.1
A
Crawlability
no robots.txt, sitemap with 4 URLs
PASS
no robots.txt, sitemap with 4 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps

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

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 200 OK
Type Sitemap Index URLs 4 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
rodizio.ro — via TES Euro Media SRL, 6 years, 2 months old, hosted on GNET-AS - Tes Euro Media SRL, RO
PASS
rodizio.ro — via TES Euro Media SRL, 6 years, 2 months old, hosted on GNET-AS - Tes Euro Media SRL, RO
Info::
Registrar: TES Euro Media 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: GNET-AS - Tes Euro Media SRL, RO
Got: AS51295
Domain expiry

Unknown

SSL certificate

60 days

Issued by Let's Encrypt

Domain age

6 years, 2 months

Registered September 7, 2020

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

GNET-AS - Tes Euro Media SRL, RO

ASN AS51295

185.248.197.90

Registrar

TES Euro Media 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 TES Euro Media SRL
Created September 7, 2020 (6 years, 2 months ago)
Name Servers ns1.fortza.net, ns2.fortza.net
Hosting
IP Address 185.248.197.90
ASN AS51295 (GNET-AS - Tes Euro Media SRL, RO)
Provider GNET-AS - Tes Euro Media SRL, RO
Data source: whois (0.6s)

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

Connection waterfall

DNS Lookup 134 ms TCP Connect 54 ms TLS Handshake 57 ms Server Processing 160 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