artemishospitals.com security report

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

42risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

4Medium

4Low

2Info

Collected 15 hours ago51.1sfrom cache

Certificate Transparency33
DNS resolution19
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs31
Registration
DNS posture2
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis10

noteFound 33 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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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.artemishospitals.com/
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.artemishospitals.com/
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.artemishospitals.com/
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://www.artemishospitals.com/
demo.artemishospitals.com 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: demo.artemishospitals.com
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.artemishospitals.com/
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.artemishospitals.com/
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: artemishospitals.com
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: artemishospitals.com
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: artemishospitals.com

final https://www.artemishospitals.com/status 200time 1254msstack 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 ASP.NET_SessionId
no Secure · HttpOnly · SameSite=lax

✓Receives mail via 1 server
artemishospitals-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com include:spfa.cpmails.com ip4:13.126.94.72 -all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; rua=mailto:dmarc_rua@artemishospitals.com; ruf=mailto:dmarc_ruf@artemishospitals.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
clay.ns.cloudflare.com roxy.ns.cloudflare.com

✓Registered with GoDaddy.com, LLC14.1 years old
artemishospitals.com
✓Registration expiry330 days
2027-08-03
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
clay.ns.cloudflare.com roxy.ns.cloudflare.com

Address	Ports	Edge	Network
172.67.222.86 www.artemishospitals.com +8	80443205220532082208320862087+5	Cloudflare~	—
104.21.17.56 www.artemishospitals.com +8	80443205220532082208320862087+5	Cloudflare~	—
3.6.219.203 care.artemishospitals.com +2	80443	direct	—
13.205.188.136 care.artemishospitals.com +2	80443	direct	—
182.76.176.66 connect.artemishospitals.com +2	443	direct	—
14.195.47.105 ris.artemishospitals.com	none known	direct	—
185.199.52.76 enquire.artemishospitals.com	none known	direct	—

Archived URLs

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

artemishospitals.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames