Skip to content
https://dripclient.in

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
2
REVIEW
11
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
4 PASS 11 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 207ms across 3 resolvers (spread 381ms)
FIX
Mean 207ms across 3 resolvers (spread 381ms)
Info::
Google: 16ms
Got: 16ms via 8.8.8.8:53
Info::
Quad9: 210ms
Got: 210ms via 9.9.9.9:53
Info::
Cloudflare: 397ms
Got: 397ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 381ms (min 16ms / max 397ms)
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.
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 202.63.243.186 does not match any cert SAN: fishtail.mysecurecloudserver.com
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
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 301

www / non-www

200https://www.dripclient.in/
200https://dripclient.in/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://dripclient.in/ → https://dripclient.in/

Consistent

B
Domain Intelligence
dripclient.in — via Atak Domain Bilgi Teknolojileri AS, 11 months old, hosted on SUBISU-CABLENET-AS-AP - Subisu Cablenet (Pvt) Ltd, Baluwatar, Kathmandu, Nepal, NP
REVIEW
dripclient.in — via Atak Domain Bilgi Teknolojileri AS, 11 months old, hosted on SUBISU-CABLENET-AS-AP - Subisu Cablenet (Pvt) Ltd, Baluwatar, Kathmandu, Nepal, NP
Critical::
Domain expires in 30 days
This domain expires on December 10, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires Dec 10, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Atak Domain Bilgi Teknolojileri AS
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: SUBISU-CABLENET-AS-AP - Subisu Cablenet (Pvt) Ltd, Baluwatar, Kathmandu, Nepal, NP
Got: AS4007
Domain expiry

28 days

December 10, 2026

SSL certificate

82 days

Issued by Let's Encrypt

Domain age

11 months

Registered December 10, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SUBISU-CABLENET-AS-AP - Subisu Cablenet (Pvt) Ltd, Baluwatar, Kathmandu, Nepal, NP

ASN AS4007

202.63.243.186

Registrar

Atak Domain Bilgi Teknolojileri AS

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Atak Domain Bilgi Teknolojileri AS
Created December 10, 2025 (11 months ago)
Expires December 10, 2026 (1 months)
Last Updated August 5, 2026
Name Servers ns1.fishtail.mysecurecloudserver.com, ns2.fishtail.mysecurecloudserver.com
DNSSEC Not enabled
Hosting
IP Address 202.63.243.186
ASN AS4007 (SUBISU-CABLENET-AS-AP - Subisu Cablenet (Pvt) Ltd, Baluwatar, Kathmandu, Nepal, NP)
Provider SUBISU-CABLENET-AS-AP - Subisu Cablenet (Pvt) Ltd, Baluwatar, Kathmandu, Nepal, NP
Data source: rdap (0.6s)

This domain expires on December 10, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

B
HTTP Probe Timing
Total 1168 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
406 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
190 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
193 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.17 s
Total Time Total request time from DNS lookup through full response.
1.17 s

Connection waterfall

DNS Lookup 406 ms TCP Connect 190 ms TLS Handshake 193 ms Server Processing 379 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
82 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

82
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, 419 ms lookup
PASS
1 A records, 419 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 202.63.243.186
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.fishtail.mysecurecloudserver.com, ns1.fishtail.mysecurecloudserver.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (419 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 419 ms
A202.63.243.186
AAAA—
CNAME—
NSns2.fishtail.mysecurecloudserver.com, ns1.fishtail.mysecurecloudserver.com
MX
0 dripclient.in
TXT
google-site-verification=IN0w-_bXzG2KA52x_Ym-aeB3k-d5zXpV1biWNM29tAQ
SPF v=spf1 +a +mx +ip4:202.63.243.186 ~all
CAALookup not available with standard resolver
Resolved in 419 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 redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://dripclient.in

https://dripclient.in

594 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dripclient.in200594 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 732 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 732 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Allow: /favicon.ico
Allow: /site.webmanifest
Allow: /browserconfig.xml
Allow: /assets/
Allow: /assets/img/
Allow: /assets/img/favicons/
Allow: /assets/css/
Allow: /assets/js/

# Private / account / auth flows — no SEO value, keep out of the index
Disallow: /admin/
Disallow: /api/
Disallow: /config/
Disallow: /includes/
Disallow: /install.php
Disallow: /cart.php
Disallow: /checkout.php
Disallow: /orders.php
Disallow: /profile.php
Disallow: /settings.php
Disallow: /reseller-dashboard.php
Disallow: /google-login.php
Disallow: /google-callback.php
Disallow: /forgot-password.php
Disallow: /reset-password.php
Disallow: /assets/uploads/reseller_payments/

Sitemap: https://dripclientseller.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 6 entries Valid XML Yes
Sample URLs:
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback