univ-tln.fr security report

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

39risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

4Medium

2Low

2Info

Collected 2 hours ago73.6sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs1
Registration
DNS posture2
Email authentication2
Certificate
Security headers2
Archived URLs
Analysis8

noteCertificate Transparency did not complete (HTTP 502). Results below are partial.
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.univ-tln.fr/
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.univ-tln.fr/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: univ-tln.fr
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: univ-tln.fr
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.univ-tln.fr/
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: univ-tln.fr
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: univ-tln.fr
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: univ-tln.fr

final https://www.univ-tln.fr/status 200time 16565msstack cloudflare · WordPress 7.1

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

✓Receives mail via 2 servers
mx1.relay.renater.fr mx2.relay.renater.fr
!SPFends in ~all
v=spf1 mx ip4:193.49.96.52/32 ip4:194.214.84.20/32 ip4:194.214.84.16/32 ip4:194.214.84.40/32 ip4:212.227.126.135/32 include:spf.partage.renater.fr include:spf.relay.renater.fr ~all
!DMARCp=none
v=DMARC1; p=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
dns.inria.fr rhodes.univ-tln.fr

✓Registered with GIP RENATER31.7 years old
univ-tln.fr
✓Registration expiry115 days
2026-12-31
✗Transfer lock
none
✓2 nameservers at registry
dns.inria.fr rhodes.univ-tln.fr

Address	Ports	CVEs	Edge	Network
193.49.96.1 univ-tln.fr +1	53	0	direct	—

Archived URLs

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

univ-tln.fr security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames