floatingislandapps.com security report

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

79risk

Critical

Exposed services or known CVEs need attention now.

0Critical

3High

5Medium

5Low

2Info

Collected 3 hours ago9.2sfrom cache

Certificate Transparency16
DNS resolution27
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs26
Registration
DNS posture2
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis15

noteFound 14 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.

Shodan matched these CVEs against the service banners it saw on 120.26.42.193 (admin.floatingislandapps.com), which advertise nginx 1.20.1. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2025-23419 CVE-2023-44487 CVE-2021-3618
What to do
Confirm the running versions on 120.26.42.193 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗CVE-2021-3618 ↗
asset: 120.26.42.193
Nothing tells receiving mail servers which hosts may send as @floatingislandapps.com, so anyone can. Phishing that impersonates this domain will land in inboxes.
What to do
Publish an SPF TXT record listing your senders and ending in -all.
asset: floatingislandapps.com
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.floatingislandapps.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@floatingislandapps.com"`, review the reports, then move to p=quarantine and p=reject.
asset: floatingislandapps.com
120.26.42.193 (admin.floatingislandapps.com) reports nginx 1.20.1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 120.26.42.193
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://floatingislandapps.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://floatingislandapps.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://floatingislandapps.com/
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: floatingislandapps.com
admin.floatingislandapps.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: admin.floatingislandapps.com
test.floatingislandapps.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: test.floatingislandapps.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://floatingislandapps.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://floatingislandapps.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: floatingislandapps.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: floatingislandapps.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: floatingislandapps.com

final https://floatingislandapps.com/status 200time 505msstack cloudflare

–http:// redirects to https://port 80 did not answer
✗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

✓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
✗SPF
no record
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
vip3.alidns.com vip4.alidns.com

✓Registered with Alibaba Cloud Computing (Beijing) Co., Ltd.5.5 years old
floatingislandapps.com
✓Registration expiry188 days
2027-03-15
✗Transfer lock
none
✓2 nameservers at registry
vip3.alidns.com vip4.alidns.com

Address	Ports	CVEs	Edge	Network
163.181.201.185 api.floatingislandapps.com +3	804438431935	0	direct	—
163.181.201.188 api.floatingislandapps.com +3	804431935	0	direct	—
163.181.201.183 api.floatingislandapps.com +3	804431935	0	direct	—
163.181.201.184 api.floatingislandapps.com +3	804431935	0	direct	—
163.181.201.186 api.floatingislandapps.com +3	804431935	0	direct	—
120.26.42.193 admin.floatingislandapps.com +1	8018019	3	direct	—
163.181.201.187 api.floatingislandapps.com +2	80443	0	direct	—
163.181.201.182 api.floatingislandapps.com +2	80443	0	direct	—
163.181.201.189 api.floatingislandapps.com +2	80443	0	direct	—
139.196.232.118 test.floatingislandapps.com +1	80	0	direct	—
47.97.41.118 derper.floatingislandapps.com	80	0	direct	—
47.110.41.105 floatingislandapps.com +3	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.

floatingislandapps.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames