Check-Host.cc

Domain

aisoft.jp

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

Run a live full scan of aisoft.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
24
A/AAAA targets
Subdomains
5
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
8
in our scans

DNS Records

A
18.239.69.105, 18.239.69.7, 18.239.69.80, 18.239.69.98, 18.66.112.108, 18.66.112.48, 18.66.112.7, 18.66.112.85
AAAA
MX
NS
ns-1119.awsdns-11.org, ns-1848.awsdns-39.co.uk, ns-441.awsdns-55.com, ns-841.awsdns-41.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

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

Tech Stack

Tech detection pending

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

TLS Certificates

Subject: *.flex-tokaisoft.jp
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: *.flex-tokaisoft.jp, flex-tokaisoft.jp
Subject: aisoft.jp
Issuer: Amazon RSA 2048 M04
SANs: *.aisoft.jp, aisoft.jp
Subject: aisoft.jp
Issuer: Amazon RSA 2048 M04
SANs: *.aisoft.jp, aisoft.jp
Subject: aisoft.jp
Issuer: Amazon RSA 2048 M01
SANs: *.stg.aisoft.jp, aisoft.jp
Subject: *.flex-tokaisoft.jp
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: *.flex-tokaisoft.jp, flex-tokaisoft.jp
Subject: *.flex-tokaisoft.jp
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: *.flex-tokaisoft.jp, flex-tokaisoft.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.

CT-Log Evidence

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

e574925fc891299f… google · xenon2026h2
Subject: *.aisoft.jp
Issuer: Amazon RSA 2048 M04
SANs: *.aisoft.jp, aisoft.jp
Valid: 2026-03-16 00:00:00 → 2026-09-29 23:59:59
32ef6b51c10a5677… google · xenon2026h2
Subject: aisoft.jp
Issuer: Amazon RSA 2048 M04
SANs: aisoft.jp, *.aisoft.jp
Valid: 2026-03-10 00:00:00 → 2026-09-23 23:59:59
a559e349f6860382… google · xenon2026h2
Subject: *.aisoft.jp
Issuer: Amazon RSA 2048 M01
SANs: *.aisoft.jp, aisoft.jp
Valid: 2026-02-22 00:00:00 → 2026-09-07 23:59:59

Threat Intelligence

Domain threat-intel pending

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

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.