kannikar.net security report

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

92risk

Critical

Exposed services or known CVEs need attention now.

2Critical

2High

8Medium

5Low

2Info

Collected 2 hours ago51.3sfrom cache

Certificate Transparency3
DNS resolution3
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs17
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 185.73.8.101 (kannikar.net), which advertise mariadb 10.11.11-MariaDB-cll-lve, openssh 8.0, exim 4.98.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-66141 CVE-2026-66140 CVE-2026-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-48840 CVE-2026-45185 CVE-2026-40687 CVE-2026-40686 CVE-2026-40685 ...and 21 more
What to do
Confirm the running versions on 185.73.8.101 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗CVE-2026-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗
asset: 185.73.8.101
Shodan matched these CVEs against the service banners it saw on 204.111.144.27 (screenshots.kannikar.net), which advertise http server 2.4.65, openssl 3.0.19. 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-49975 CVE-2026-48913 CVE-2026-45447 CVE-2026-45446 CVE-2026-45445 CVE-2026-44631 CVE-2026-44186 CVE-2026-44185 CVE-2026-44119 CVE-2026-43951 CVE-2026-42770 CVE-2026-42767 CVE-2026-42766 CVE-2026-42536 CVE-2026-42535 ...and 46 more
What to do
Confirm the running versions on 204.111.144.27 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-48913 ↗CVE-2026-45447 ↗CVE-2026-45446 ↗CVE-2026-45445 ↗
asset: 204.111.144.27
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.73.8.101:3306
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.kannikar.net TXT "v=DMARC1; p=none; rua=mailto:dmarc@kannikar.net"`, review the reports, then move to p=quarantine and p=reject.
asset: kannikar.net
185.73.8.101 (kannikar.net) reports mariadb 10.11.11-MariaDB-cll-lve, openssh 8.0, exim 4.98.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: 185.73.8.101
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.73.8.101:21
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.73.8.101:22
204.111.144.27 (screenshots.kannikar.net) reports http server 2.4.65, openssl 3.0.19. 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: 204.111.144.27
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://kannikar.net/
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://kannikar.net/
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://kannikar.net/
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: kannikar.net
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.73.8.101:25
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://kannikar.net/
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://kannikar.net/
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://kannikar.net/
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: kannikar.net
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: kannikar.net
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: kannikar.net

final https://kannikar.net/status 200time 1096msstack 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 PHPSESSID
Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
mail.kannikar.net
!SPFends in ~all
v=spf1 a mx ip4:185.73.8.101 include:spf.hostns.io ~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
ns1n815.extrainfra.com ns2n815.extrainfra.com

✓Registered with NameCheap, Inc.4.0 years old
kannikar.net
✓Registration expiry355 days
2027-08-28
✗Transfer lock
none
✓2 nameservers at registry
ns1n815.extrainfra.com ns2n815.extrainfra.com

Address	Ports	CVEs	Edge	Network
185.73.8.101 kannikar.net +4	21222580110143443465+6	36	direct	—
204.111.144.27 screenshots.kannikar.net	804435678	61	direct	—

Archived URLs

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

kannikar.net security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames