Skip to content
https://fortzasteel.ro

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
9
PASS
5
INFO
1
Probed from Sao Paulo, Brazil
200 OK
Checks
17
5 PASS 9 REVIEW 2 FIX
F
HTTP Probe Timing
Action
Total 13325 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
1.57 s
TCP Connect TCP Connect — time to establish a TCP connection to the server.
226 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
230 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
12.66 s
Total Time Total request time from DNS lookup through full response.
13.33 s

Connection waterfall

DNS Lookup 1.57 s TCP Connect 226 ms TLS Handshake 230 ms Server Processing 10.64 s Content Transfer 664 ms
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

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.
C
Multi-Resolver DNS Speed
Action
Mean 288ms across 3 resolvers (spread 265ms)
REVIEW
Mean 288ms across 3 resolvers (spread 265ms)
Info::
Cloudflare: 189ms
Got: 189ms via 1.1.1.1:53
Info::
Quad9: 222ms
Got: 222ms via 9.9.9.9:53
Info::
Google: 454ms
Got: 454ms via 8.8.8.8:53
Info::
High latency spread between resolvers: 265ms (min 189ms / max 454ms)
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.
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
53 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

53
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
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, 972 ms lookup
PASS
1 A records, 972 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
Warning::
DNS resolution is slow (972 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 972 ms
A185.248.197.90
AAAA—
CNAME—
NSns2.fortza.net, ns1.fortza.net
MX
0 fortzasteel.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...
CAALookup not available with standard resolver
Resolved in 972 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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirect data available
PASS
No redirect data available
Info::
No redirect data captured
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 1236 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 1236 B Sitemaps referenced 1 User-agents Yandex, * Blocking No — crawling allowed
User-agent: Yandex

Disallow: /wp-admin

Disallow: /wp-includes

Disallow: /wp-login.php

Disallow: /wp-register.php

Disallow: /wp-content/themes

Disallow: /wp-content/plugins

Disallow: /wp-content/upgrade

Disallow: /wp-content/themes_backup

Disallow: /wp-content/cache

Disallow: /xmlrpc.php

Disallow: /template.html

Disallow: /wp-comments

Disallow: /cgi-bin

Disallow: /trackback

Disallow: /feed

Disallow: /comments

Disallow: /comment-page

Disallow: /replytocom=

Disallow: /author

Disallow: /?author=

Disallow: /tag

Disallow: /?feed=

Disallow: /?s=

Disallow: /?se=


User-agent: *

Disallow: /wp-admin

Disallow: /wp-includes

Disallow: /wp-login.php

Disallow: /wp-register.php

Disallow: /wp-content/themes

Disallow: /wp-content/plugins

Disallow: /wp-content/upgrade

Disallow: /wp-content/themes_backup

Disallow: /wp-content/cache

Disallow: /xmlrpc.php

Disallow: /template.html

Disallow: /wp-comments

Disallow: /cgi-bin

Disallow: /trackback

Disallow: /feed

Disallow: /comments

Disallow: /comment-page

Disallow: /replytocom=

Disallow: /author

Disallow: /?author=

Disallow: /tag

Disallow: /?feed=

Disallow: /?s=

Disallow: /?se=


Host: fortzasteel.ro
Sitemap: https://fortzasteel.ro/sitemap.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: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.fortzasteel.ro/
200https://fortzasteel.ro/

Preferred variant: non-www

HTTP → HTTPS

301http://fortzasteel.ro/ → https://fortzasteel.ro/

Consistent

Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback