Infrastructure - https://beta.locumnet.in BeaverCheck Audit

B

DNS Records

2 A records, 31 ms lookup

REVIEW

2 A records, 31 ms lookup

Resolves to 2 IPv4 address(es)

Got: 63.176.8.218, 35.157.26.135

Has 2 IPv6 (AAAA) record(s)

Got: 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: genuine-taiyaki-487ea1.netlify.app

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

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

DNS resolution time: 31 ms

Got: 31 ms

A	63.176.8.218, 35.157.26.135
AAAA	2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258
CNAME	genuine-taiyaki-487ea1.netlify.app
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 31 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

B

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

B

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.

B

Reverse DNS

0/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR for 63.176.8.218 does not match any cert SAN: ec2-63-176-8-218.eu-central-1.compute.amazonaws.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.

PTR for 35.157.26.135 does not match any cert SAN: ec2-35-157-26-135.eu-central-1.compute.amazonaws.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.

PTR lookup failed for 2a05:d014:58f:6200::259: lookup 2a05:d014:58f:6200::259: 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.

PTR lookup failed for 2a05:d014:58f:6200::258: lookup 2a05:d014:58f:6200::258: 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

88 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

88

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

CDN & Delivery

Netlify

REVIEW

Netlify

Site is served via Netlify CDN

Got: x-nf-request-id: 01M1ESH8778T2KK7HGB26Y6DYH

CDN Detected: Netlify

Provider Netlify Evidence x-nf-request-id: 01M1ESH8778T2KK7HGB26Y6DYH

B

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.

B

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.

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A+

Multi-Resolver DNS Speed

Mean 35ms across 3 resolvers (spread 18ms)

PASS

Mean 35ms across 3 resolvers (spread 18ms)

Cloudflare: 28ms

Got: 28ms via 1.1.1.1:53

Google: 32ms

Got: 32ms via 8.8.8.8:53

Quad9: 46ms

Got: 46ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://beta.locumnet.in

https://beta.locumnet.in

219 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://beta.locumnet.in	200	219 ms	HTTP/1.1	Netlify

A+

IPv6 Readiness

IPv6 reachable (28 ms)

PASS

IPv6 reachable (28 ms)

IPv6 is configured and reachable at 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258

Got: 28 ms connect

IPv6 Ready

AAAA Records 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258 Connection Reachable (28 ms)

A+

Crawlability

robots.txt present, sitemap with 1 URLs

PASS

robots.txt present, sitemap with 1 URLs

robots.txt is present

Got: 499 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 1 entries

robots.txt references sitemap

robots.txt 200 OK

Size 499 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Allow: /
Disallow: /pages/admin/
Disallow: /pages/auth/
Disallow: /pages/doctors/dashboard.html
Disallow: /pages/doctors/complete-profile.html
Disallow: /pages/doctors/profile.html
Disallow: /pages/hospitals/dashboard.html
Disallow: /pages/hospitals/profile.html
Disallow: /pages/hospitals/post-requirement.html
Disallow: /pages/hospitals/post-urgent-requirement.html
Disallow: /pages/hospitals/post-permanent-job.html
Disallow: /pages/locum/

Sitemap: https://locumnet.in/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 1 entries Valid XML Yes

Sample URLs:

https://locumnet.in/lander

A+

URL Variants

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

PASS

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

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

https://www.beta.locumnet.in/

200https://beta.locumnet.in/

HTTP → HTTPS

301http://beta.locumnet.in/ → https://beta.locumnet.in/

Consistent

A+

Domain Intelligence

locumnet.in — via GoDaddy, 3 months old, hosted on AWS

PASS

locumnet.in — via GoDaddy, 3 months old, hosted on AWS

Domain registered until May 19, 2027 (8 months remaining)

Domain is only 3 months 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 May 19, 2026

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: AWS

Got: AS16509

Domain expiry

259 days

May 19, 2027

SSL certificate

88 days

Issued by Let's Encrypt

Domain age

3 months

Registered May 19, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

15.197.148.33

Registrar

GoDaddy

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Newly registered domain — build backlinks and content to establish SEO trust
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar GoDaddy

Created May 19, 2026 (3 months ago)

Expires May 19, 2027 (8 months)

Last Updated August 22, 2026

Name Servers ns37.domaincontrol.com, ns38.domaincontrol.com

DNSSEC Not enabled

Hosting

IP Address 15.197.148.33

ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (0.8s)

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.

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

A

HTTP Probe Timing

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

PASS

DNS Lookup

40 ms

TCP Connect

33 ms

TLS Handshake

148 ms

Time to First Byte

454 ms

Total Time

454 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 33 ms TLS Handshake 148 ms Server Processing 233 ms Content Transfer 0 ms

A+

CDN Cache Observability

Cache state: Age=1s

PASS

Cache state: Age=1s

CDN cache state observable via 1 header(s)

Got: age=1