Skip to content
https://netzhi.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
5
PASS
12
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
12 PASS 5 REVIEW
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 188.114.97.2: lookup 188.114.97.2: 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 188.114.96.2: lookup 188.114.96.2: 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:3121::2: lookup 2a06:98c1:3121::2: 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:3120::2: lookup 2a06:98c1:3120::2: 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
86 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 51 ms lookup
PASS
2 A records, 51 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.97.2, 188.114.96.2
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3121::2, 2a06:98c1:3120::2
Info::
2 nameserver(s) configured
Got: jasper.ns.cloudflare.com, raina.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 51 ms
Got: 51 ms
A188.114.97.2, 188.114.96.2
AAAA2a06:98c1:3121::2, 2a06:98c1:3120::2
CNAME—
NSjasper.ns.cloudflare.com, raina.ns.cloudflare.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 51 ms

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A+
Multi-Resolver DNS Speed
Mean 38ms across 3 resolvers (spread 36ms)
PASS
Mean 38ms across 3 resolvers (spread 36ms)
Info::
Cloudflare: 25ms
Got: 25ms via 1.1.1.1:53
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
Info::
Quad9: 61ms
Got: 61ms 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://netzhi.com

https://netzhi.com

92 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://netzhi.com20092 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3121::2, 2a06:98c1:3120::2
Got: 17 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3121::2, 2a06:98c1:3120::2 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 111 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 111 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://netzhi.com/wp-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 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.netzhi.com/
200https://netzhi.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
netzhi.com — via NameSilo, LLC, 3 days old
PASS
netzhi.com — via NameSilo, LLC, 3 days old
Info::
Domain registered until Nov 4, 2027 (1 years remaining)
Info::
Domain is only 3 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Nov 4, 2026
Info::
DNSSEC is enabled
Info::
Registrar: NameSilo, 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.
Domain expiry

360 days

November 4, 2027

SSL certificate

86 days

Issued by Let's Encrypt

Domain age

3 days

Registered November 4, 2026

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3121::2

Registrar

NameSilo, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NameSilo, LLC
Created November 4, 2026 (3 days ago)
Expires November 4, 2027 (1 years)
Last Updated November 5, 2026
Name Servers jasper.ns.cloudflare.com, raina.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2a06:98c1:3121::2
Data source: rdap (0.2s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

Connection waterfall

DNS Lookup 53 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 35 ms Content Transfer 1 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a57592af8dbecc0a-CDG
Info::
CDN cache status: HIT
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: a57592af8dbecc0a-CDG
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=4774, 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