Infrastructure

· 16 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

200 OK

Checks

4 PASS 11 REVIEW 1 FIX

Multi-Resolver DNS Speed

Action

Mean 565ms across 3 resolvers (spread 705ms)

FIX

Mean 565ms across 3 resolvers (spread 705ms)

Google: 313ms

Got: 313ms via 8.8.8.8:53

Quad9: 365ms

Got: 365ms via 9.9.9.9:53

Cloudflare: 1018ms

Got: 1018ms via 1.1.1.1:53

High latency spread between resolvers: 705ms (min 313ms / max 1018ms)

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.

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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).

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

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.

Reverse DNS

1 PTR record(s) found (no cert data to match against)

REVIEW

1 PTR record(s) found (no cert data to match against)

PTR for 148.113.20.194: bighost.s2.mysecurecloudhost.in

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

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

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

www / non-www

200http://www.easybankloans.co.in/

200http://easybankloans.co.in/

Inconsistent — duplicate content risk

HTTP Probe Timing

Total 1108 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

643 ms

TCP Connect

230 ms

TLS Handshake

0 ms

Time to First Byte

1.11 s

Total Time

1.11 s

Connection waterfall

DNS Lookup 643 ms TCP Connect 230 ms TLS Handshake 0 ms Server Processing 236 ms Content Transfer 0 ms

CDN & Delivery

Action

Assets on Cloudflare (host i.pravatar.cc, 4 assets); document served directly from origin (OVH)

REVIEW

Assets on Cloudflare (host i.pravatar.cc, 4 assets); document served directly from origin (OVH)

Document not behind existing CDN (Cloudflare serves the assets)

The page's subresources are delivered by Cloudflare (i.pravatar.cc, 4 assets), but the HTML document itself comes straight from the origin (OVH). 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: a55b040d7ecf3b64-CDG

Assets on Cloudflare: i.pravatar.cc (assets: 4), cache HIT

Got: cf-ray: a55b040d7ecf3b64-CDG

Assets on a CDN, document is not: Cloudflare

Document origin OVH

Asset hosts on a CDN

i.pravatar.cc — Cloudflare · assets: 4 · Cache Status: HIT

Other asset hosts

images.unsplash.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.

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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.

Operational Status Page

No status page link detected

REVIEW

No status page link detected

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.

Health Check Endpoint

No conventional health endpoint found

REVIEW

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.

DNS Records

1 A records, 628 ms lookup

PASS

1 A records, 628 ms lookup

Resolves to 1 IPv4 address(es)

Got: 148.113.20.194

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns2.mysecurecloudhost.in, ns1.mysecurecloudhost.in

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (628 ms)

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

Got: 628 ms

A	148.113.20.194
AAAA	—
CNAME	—
NS	ns2.mysecurecloudhost.in, ns1.mysecurecloudhost.in
MX	0 easybankloans.co.in
TXT	SPF v=spf1 ip4:148.113.20.194 +a +mx +ip4:148.113.8.54 +ip4:148.113.27.14 +ip4:103.1...
CAA	Lookup not available with standard resolver

Resolved in 628 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

No CNAME record present

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: http://easybankloans.co.in

http://easybankloans.co.in

457 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	http://easybankloans.co.in	200	457 ms	HTTP/1.1	LiteSpeed

A+

Domain Intelligence

easybankloans.co.in — via GoDaddy, 1 years, 8 months old, hosted on OVH

PASS

easybankloans.co.in — via GoDaddy, 1 years, 8 months old, hosted on OVH

Domain registered until Mar 10, 2027 (4 months remaining)

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.

Registrar: GoDaddy

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.

Hosting: OVH

Got: AS16276

Domain expiry

121 days

March 10, 2027

SSL certificate

No certificate data

Domain age

1 years, 8 months

Registered March 10, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

148.113.20.194

Registrar

GoDaddy

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar GoDaddy

Created March 10, 2025 (1 years, 8 months ago)

Expires March 10, 2027 (4 months)

Last Updated May 11, 2026

Name Servers ns2.cloud19.in, ns1.cloud19.in

DNSSEC Not enabled

Hosting

IP Address 148.113.20.194

ASN AS16276 (OVH - OVH SAS, FR)

Provider OVH

Data source: rdap (0.6s)

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

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