kintone.com security report

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

43risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

4Medium

5Low

2Info

Collected 13 hours ago9.2sfrom cache

Certificate Transparency
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs0
Registration
DNS posture4
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis11

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.kintone.com/en-sea/
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.kintone.com/en-sea/
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.kintone.com/en-sea/
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.kintone.com/en-sea/
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.kintone.com/en-sea/
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.kintone.com/en-sea/
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://www.kintone.com/en-sea/
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://www.kintone.com/en-sea/
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: kintone.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: kintone.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: kintone.com

final https://www.kintone.com/en-sea/status 200time 1277msstack 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 pll_language
Secure · no HttpOnly · SameSite=lax
✗Cookie wordpress_select_country
no Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
kintone-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com include:mail.zendesk.com include:1857320.spf06.hubspotemail.net a:zgateway.zuora.com include:amazonses.com include:_spf.mxhero.com include:fc5038.cuenote.jp -all
✓DMARCp=reject
v=DMARC1; p=reject; pct=100; rua=mailto:7acf0af11d@rua.easydmarc.asia
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1284.awsdns-32.org ns-1730.awsdns-24.co.uk ns-188.awsdns-23.com ns-813.awsdns-37.net

✓Registered with Amazon Registrar, Inc.20.7 years old
kintone.com
✓Registration expiry96 days
2026-12-12
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1284.awsdns-32.org ns-1730.awsdns-24.co.uk ns-188.awsdns-23.com ns-813.awsdns-37.net

Address	Ports	CVEs	Edge	Network
35.86.12.188 kintone.com	none known	0	direct	—
54.190.71.52 kintone.com	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.

kintone.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames