Check-Host.cc

Domain

4keys.app

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of 4keys.app

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
8
A/AAAA targets
Subdomains
1
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
3
in our scans

DNS Records

A
13.35.58.20, 13.35.58.68, 13.35.58.71, 13.35.58.76, 18.239.36.113, 18.239.36.62, 18.239.36.68, 18.239.36.9
AAAA
MX
NS
ns-1088.awsdns-08.org, ns-1872.awsdns-42.co.uk, ns-288.awsdns-36.com, ns-541.awsdns-03.net
TXT
CNAME
CAA

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain Resolves to Last seen
4keys.app 2026-06-21 04:39:39.233

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

41743a45cb5da4a7… google · argon2026h2
Subject: 4keys.app
Issuer: Amazon RSA 2048 M04
SANs: 4keys.app
Valid: 2025-09-16 00:00:00 → 2026-10-15 23:59:59
18ab57f0b1e4b942… google · argon2026h2
Subject: 4keys.app
Issuer: Amazon RSA 2048 M01
SANs: 4keys.app
Valid: 2025-09-14 00:00:00 → 2026-10-13 23:59:59
f6bcf2492bfd48d9… google · argon2026h2
Subject: 4keys.app
Issuer: Amazon RSA 2048 M01
SANs: 4keys.app
Valid: 2025-09-14 00:00:00 → 2026-10-13 23:59:59

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
NS ns-541.awsdns-03.net 2026-06-21 04:24:53.477 2026-06-21 04:39:39.233
A 13.35.58.68 2026-06-21 04:24:53.477 2026-06-21 04:39:39.233
NS ns-1872.awsdns-42.co.uk 2026-06-21 04:24:53.477 2026-06-21 04:39:39.233
NS ns-288.awsdns-36.com 2026-06-21 04:24:53.477 2026-06-21 04:39:39.233
A 13.35.58.20 2026-06-21 04:24:53.477 2026-06-21 04:39:39.233
A 13.35.58.71 2026-06-21 04:24:53.477 2026-06-21 04:39:39.233
NS ns-1088.awsdns-08.org 2026-06-21 04:24:53.477 2026-06-21 04:39:39.233
A 13.35.58.76 2026-06-21 04:24:53.477 2026-06-21 04:39:39.233
A 18.239.36.9 2026-06-21 04:28:48.333 2026-06-21 04:28:48.333
A 18.239.36.113 2026-06-21 04:28:48.333 2026-06-21 04:28:48.333
A 18.239.36.68 2026-06-21 04:28:48.333 2026-06-21 04:28:48.333
A 18.239.36.62 2026-06-21 04:28:48.333 2026-06-21 04:28:48.333