librarie.net security report

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

36risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

3Medium

5Low

2Info

Collected 19 hours ago4.3sfrom cache

Certificate Transparency24
DNS resolution4
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2
Registration
DNS posture2
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis10

noteFound 24 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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://www.librarie.net/bf.php
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://www.librarie.net/bf.php
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://www.librarie.net/bf.php
test.librarie.net 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: test.librarie.net
www.test.librarie.net 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: www.test.librarie.net
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://www.librarie.net/bf.php
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://www.librarie.net/bf.php
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: librarie.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: librarie.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: librarie.net

final https://www.librarie.net/bf.phpstatus 200time 1939msstack 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

✓Receives mail via 1 server
librarie.net
✓SPFends in -all
v=spf1 mx a ip4:72.52.158.200 -all
✓DMARCp=reject
v=DMARC1; p=reject; sp=reject;
!MTA-STSinbound mail can be downgraded to plaintext

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

✓Registered with NameCheap, Inc.24.4 years old
librarie.net
✓Registration expiry603 days
2028-05-02
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns.liquidweb.com ns1.liquidweb.com

Address	Ports	CVEs	Edge	Network
72.52.158.200 librarie.net +3	80443	0	direct	—

Archived URLs

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

librarie.net security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames