Check-Host.cc

Domain

kiban.jp

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

Run a live full scan of kiban.jp

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
1
A/AAAA targets
Subdomains
6
CT + scan + body
Record Types
4
seen in DNS
Observed Certs
2
in our scans

DNS Records

A
210.140.87.95
AAAA
MX
1 aspmx.l.google.com, 10 alt3.aspmx.l.google.com, 10 alt4.aspmx.l.google.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
ns-1465.awsdns-55.org, ns-1881.awsdns-43.co.uk, ns-40.awsdns-05.com, ns-929.awsdns-52.net
TXT
v=spf1 +ip4:113.35.118.120 +ip4:52.68.89.187 +ip4:122.208.207.178 +ip4:211.120.60.68 +ip4:211.120.60.63 +ip4:210.140.87.109 include:_spf.google.com ~all
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
kiban.jp 2026-06-14 23:07:05.130
www.kiban.jp 2026-06-14 23:07:05.130

Tech Stack

Tech detection pending

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

TLS Certificates

Subject: www.kiban.jp
Issuer: FujiSSL RSA Domain Validation Secure Server CA 2
SANs: kiban.jp, www.kiban.jp
Subject: www.kiban.jp
Issuer: FujiSSL RSA Domain Validation Secure Server CA 2
SANs: kiban.jp, www.kiban.jp

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.

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-40.awsdns-05.com 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
NS ns-1465.awsdns-55.org 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
MX 5 alt2.aspmx.l.google.com 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
MX 10 alt4.aspmx.l.google.com 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
MX 1 aspmx.l.google.com 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
NS ns-1881.awsdns-43.co.uk 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
TXT v=spf1 +ip4:113.35.118.120 +ip4:52.68.89.187 +ip4:122.208.207.178 +ip4:211.120.60.68 +ip4:211.120.60.63 +ip4:210.140.87.109 include:_spf.google.com ~all 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
MX 5 alt1.aspmx.l.google.com 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
MX 10 alt3.aspmx.l.google.com 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
NS ns-929.awsdns-52.net 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130
A 210.140.87.95 2026-05-26 08:19:24.378 2026-06-14 23:07:05.130