monato.com security report

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

29risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

2Medium

19Low

2Info

Collected 4 hours ago14.6sfrom cache

Certificate Transparency32
DNS resolution26
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs16
Registration
DNS posture4
Email authentication2
Certificate
Security headers2
Archived URLs
Analysis23

noteFound 32 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 18 addresses; enriching the first 12.
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.

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://monato.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://monato.com/
qa.monato.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: qa.monato.com
stg.monato.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: stg.monato.com
kora.qa.monato.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: kora.qa.monato.com
kora2.qa.monato.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: kora2.qa.monato.com
orbis.qa.monato.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: orbis.qa.monato.com
infra-test.monato.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: infra-test.monato.com
kora-api.qa.monato.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: kora-api.qa.monato.com
qa.internal.monato.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: qa.internal.monato.com
dev.internal.monato.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: dev.internal.monato.com
orbis-api.qa.monato.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: orbis-api.qa.monato.com
stg.internal.monato.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: stg.internal.monato.com
directdebit.stg.monato.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: directdebit.stg.monato.com
kora-integration-ms.qa.monato.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: kora-integration-ms.qa.monato.com
docs-old.monato.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: docs-old.monato.com
internal.monato.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: internal.monato.com
prod.internal.monato.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: prod.internal.monato.com
sharedsvcs.internal.monato.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: sharedsvcs.internal.monato.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://monato.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: monato.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: monato.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: monato.com

final https://monato.com/status 200time 242msstack cloudflare · Framer e19f2fb

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

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
!SPFends in ~all
v=spf1 include:_spf.google.com include:amazonses.com include:50593707.spf08.hubspotemail.net ~all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; rua=mailto:dmarc@monato.com; ruf=mailto:dmarc@monato.com; sp=quarantine; adkim=r; aspf=r;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1054.awsdns-03.org ns-1699.awsdns-20.co.uk ns-268.awsdns-33.com ns-932.awsdns-52.net

✓Registered with NameCheap, Inc.20.3 years old
monato.com
✓Registration expiry243 days
2027-05-08
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1054.awsdns-03.org ns-1699.awsdns-20.co.uk ns-268.awsdns-33.com ns-932.awsdns-52.net

Address	Ports	Edge	Network
31.43.161.6 www.monato.com +4	80443	direct	—
31.43.160.6 www.monato.com +4	80443	direct	—
13.224.245.28 kora.qa.monato.com +11	80443	direct	—
52.13.162.163 orbis-api.qa.monato.com +3	80443	direct	—
13.224.245.68 kora.qa.monato.com +1	80	direct	—
13.224.245.21 kora.qa.monato.com +1	80	direct	—
13.224.245.83 kora.qa.monato.com +1	80	direct	—
13.224.245.11 orbis.qa.monato.com +1	80	direct	—
13.224.245.117 orbis.qa.monato.com +1	80	direct	—
13.224.245.88 orbis.qa.monato.com +1	80	direct	—
13.224.245.121 orbis.qa.monato.com +1	80	direct	—
184.32.25.198 orbis-api.qa.monato.com +3	443	direct	—

Archived URLs

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

monato.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames