nik.io security report

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

18risk

Low

Minor observations only.

0Critical

0High

1Medium

6Low

1Info

Collected 3 hours ago2.7sfrom cache

Certificate Transparency19
DNS resolution19
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs13
Registration
DNS posture4
Email authentication2
Certificate
Security headers3
Archived URLs
Analysis8

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.
noteNo registration data: RDAP has no record at this level.

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://nik.io/
grafana.nik.io 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: grafana.nik.io
demo.nik.io 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.nik.io
b.demo.nik.io 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: b.demo.nik.io
w.demo.nik.io 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: w.demo.nik.io
discourse.demo.nik.io 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: discourse.demo.nik.io
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://nik.io/
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: nik.io

final https://nik.io/status 200time 767msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
✗Content-Security-Policy
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 6 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+2
!SPFends in ~all
v=spf1 mx:nik.io a include:_spf.google.com ~all
✓DMARCp=reject
v=DMARC1; p=reject; adkim=r; aspf=r
!MTA-STSinbound mail can be downgraded to plaintext

✓DNSSECanswers are signed and validated
✓CAA
0 issue "letsencrypt.org" · 128 issuewild "comodoca.com" · 128 issuewild "letsencrypt.org"
✓IPv6 (AAAA)
✓4 nameservers
ns1.nik.io ns2.nik.io ns3.nik.io ns4.nik.io

Address	Ports	Edge	Network
27.100.36.111 w.demo.nik.io +1	8012348181	direct	—
207.211.151.16 nik.io +19	80443	direct	—
65.108.39.169 prometheus.nik.io +5	80443	direct	—
139.99.208.166 hs.nik.io +1	1808021116	direct	—
88.99.219.135 dnsmgr.nik.io +3	80443	direct	—
46.4.94.239 mx.nik.io +3	443	direct	—
10.0.0.100 home.nik.io	161	direct	—
10.0.0.111 srv.nik.io	none known	direct	—
163.172.223.205 europa.nik.io	none known	direct	—
107.189.5.193 b.demo.nik.io	none known	direct	—

Archived URLs

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

nik.io security report

Low

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames