rncjaipur.org security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

86risk

Critical

Exposed services or known CVEs need attention now.

0Critical

4High

7Medium

6Low

2Info

Collected 1 hour ago87.2sfrom cache

Certificate Transparency14
DNS resolution11
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs25
Registration
DNS posture2
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis19

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

Shodan matched these CVEs against the service banners it saw on 103.152.79.199 (rncjaipur.org), which advertise mariadb 10.11.18-MariaDB-cll-lve, exim 4.99.2, openresty 1.31.1.1. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-48840 CVE-2026-45185
What to do
Confirm the running versions on 103.152.79.199 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-48840 ↗CVE-2026-45185 ↗
asset: 103.152.79.199
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 103.152.79.199:3306
A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://rncjaipur.org/
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.rncjaipur.org TXT "v=DMARC1; p=none; rua=mailto:dmarc@rncjaipur.org"`, review the reports, then move to p=quarantine and p=reject.
asset: rncjaipur.org
103.152.79.199 (rncjaipur.org) reports mariadb 10.11.18-MariaDB-cll-lve, exim 4.99.2, openresty 1.31.1.1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 103.152.79.199
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 103.152.79.199:21
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://rncjaipur.org/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://rncjaipur.org/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://rncjaipur.org/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://rncjaipur.org/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://rncjaipur.org/
103.171.45.41 (collegeinspection.rncjaipur.org) reports internet information services 10.0. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 103.171.45.41
admin.rncjaipur.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: admin.rncjaipur.org
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://rncjaipur.org/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://rncjaipur.org/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://rncjaipur.org/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: rncjaipur.org
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: rncjaipur.org
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: rncjaipur.org

final https://rncjaipur.org/status 200time 357msstack cloudflare

✗http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie XSRF-TOKEN
no Secure · no HttpOnly · SameSite=lax
✗Cookie laravel_session
no Secure · HttpOnly · SameSite=lax

✓Receives mail via 1 server
rncjaipur-org.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com -all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
dolly.ns.cloudflare.com matias.ns.cloudflare.com

✓Registered with PDR Ltd. d/b/a PublicDomainRegistry.com16.5 years old
rncjaipur.org
✓Registration expiry171 days
2027-02-26
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
dolly.ns.cloudflare.com matias.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
103.152.79.199 rncjaipur.org +4	215380110111443587993+13	2	direct	—
103.152.79.101 admin.rncjaipur.org +2	5380	0	direct	—
103.152.79.102 rnc.rncjaipur.org +4	80	0	direct	—
103.171.45.41 collegeinspection.rncjaipur.org +3	80	0	direct	—
103.129.97.18 examdemo.rncjaipur.org	none known	0	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

rncjaipur.org security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames