Check-Host.cc

Domain

dotnice.jp

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

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

DNS Records

A
52.85.47.108, 52.85.47.19, 52.85.47.55, 52.85.47.63
AAAA
2600:9000:2070:0:15:1f27:a640:93a1, 2600:9000:2070:2200:15:1f27:a640:93a1, 2600:9000:2070:6c00:15:1f27:a640:93a1, 2600:9000:2070:7600:15:1f27:a640:93a1, 2600:9000:2070:8200:15:1f27:a640:93a1, 2600:9000:2070:9600:15:1f27:a640:93a1, 2600:9000:2070:a200:15:1f27:a640:93a1, 2600:9000:2070:cc00:15:1f27:a640:93a1
MX
NS
ns.dotnice.asia, ns.dotnice.com, ns.dotnice.eu, ns.dotnice.zone
TXT
facebook-domain-verification=5dz9s848p31j927b1091vqpgd8ikfd, v=spf1 -all
CNAME
CAA
0 iodef "mailto:hostmaster@dotnice.com", 0 issue "amazon.com", 0 issue "amazontrust.com", 0 issue "awstrust.com", 0 issue "letsencrypt.org", 0 issuewild "amazon.com", 0 issuewild "letsencrypt.org"

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

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.

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.