l3xis.net security report

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

50risk

Elevated

Several issues worth triaging this week.

0Critical

0High

6Medium

6Low

2Info

Collected 8 hours ago10.1sfrom cache

Certificate Transparency18
DNS resolution6
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs0
Registration
DNS posture2
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis14

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.

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://l3xis.net/login
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://l3xis.net/login
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://l3xis.net/login
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://l3xis.net/login
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://l3xis.net/login
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://l3xis.net/login
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://l3xis.net/login
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://l3xis.net/login
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://l3xis.net/login
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://l3xis.net/login
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://l3xis.net/login
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: l3xis.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: l3xis.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: l3xis.net

final https://l3xis.net/loginstatus 200time 2200msstack cloudflare · PHP/7.3.33

✓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 ci_session
no Secure · HttpOnly · no SameSite
✗Cookie L3xis_c
no Secure · no HttpOnly · no SameSite
✗Cookie L3xis_c
no Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
l3xis.net
!SPFends in ~all
v=spf1 +a +mx +ip4:86.38.203.58 ~all
✓DMARCp=reject
v=DMARC1;p=reject;sp=reject;adkim=r;aspf=r;pct=100;fo=1;rf=afrf;ri=86400
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns1.l3xis.net ns2.l3xis.net

✓Registered with HOSTINGER operations, UAB6.0 years old
l3xis.net
✓Registration expiry373 days
2027-09-15
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.l3xis.net ns2.l3xis.net

Address	Ports	CVEs	Edge	Network
86.38.203.58 l3xis.net +5	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.

l3xis.net security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames