Skip to content
https://www.nepsysdigitalsolution.com.np

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
6
PASS
10
INFO
1
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 6 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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 216.198.79.65: lookup 216.198.79.65: 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 64.29.17.1: lookup 64.29.17.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
TLS Certificate Expiry & Recommendations
42 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

42
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
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.
A
DNS Records
2 A records, 44 ms lookup
PASS
2 A records, 44 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 216.198.79.65, 64.29.17.1
Info::
No IPv6 (AAAA) records
Info::
No NS records found
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: 44 ms
Got: 44 ms
A216.198.79.65, 64.29.17.1
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 44 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+
Multi-Resolver DNS Speed
Mean 28ms across 3 resolvers (spread 16ms)
PASS
Mean 28ms across 3 resolvers (spread 16ms)
Info::
Cloudflare: 21ms
Got: 21ms via 1.1.1.1:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Quad9: 37ms
Got: 37ms 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://www.nepsysdigitalsolution.com.np

https://www.nepsysdigitalsolution.com.np

204 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.nepsysdigitalsolution.com.np200204 msHTTP/1.1Vercel
A+
Crawlability
robots.txt present, sitemap with 31 URLs
PASS
robots.txt present, sitemap with 31 URLs
Info::
robots.txt is present
Got: 147 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 31 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 147 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# Robots.txt for Nepsys (https://www.nepsys.online)
User-agent: *
Allow: /

# Canonical XML Sitemap
Sitemap: https://www.nepsys.online/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 31 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 308

www / non-www

200https://www.nepsysdigitalsolution.com.np/
308https://nepsysdigitalsolution.com.np/

HTTP → HTTPS

308http://www.nepsysdigitalsolution.com.np/ → https://www.nepsysdigitalsolution.com.np/

Consistent

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

Connection waterfall

DNS Lookup 40 ms TCP Connect 1 ms TLS Handshake 41 ms Server Processing 271 ms Content Transfer 1 ms
A
CDN & Delivery
Vercel (MISS)
PASS
Vercel (MISS)
Info::
Document is served via Vercel CDN
Got: x-vercel-id: cdg1::72vlt-1793764547364-788028d8c4a8
Info::
CDN cache status: MISS
Document served via CDN: Vercel
Provider Vercel Cache Status MISS Evidence x-vercel-id: cdg1::72vlt-1793764547364-788028d8c4a8
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 2 header(s)
Got: age=0, x-vercel-cache=MISS
A+
Health Check Endpoint
Health endpoint at https://www.nepsysdigitalsolution.com.np/health (HTTP 200)
PASS
Health endpoint at https://www.nepsysdigitalsolution.com.np/health (HTTP 200)
Info::
Public health endpoint at https://www.nepsysdigitalsolution.com.np/health
Got: https://www.nepsysdigitalsolution.com.np/health
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