Check-Host.cc

Domain

jsonip.com

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

Run a live full scan of jsonip.com

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

DNS Records

A
34.160.111.145
AAAA
2600:1901:0:b2bd::
MX
NS
ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
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
jsonip.com 2026-07-28 19:39:40.097
ipv4.jsonip.com 2026-05-27 04:01:15.480

Tech Stack

Tech detection pending

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

TLS Certificates

Subject: getjsonip.com
Issuer: WR3
SANs: areacode.io, blog.ipinfo.io, city.io, country.io, getjsonip.com, www.getjsonip.com, zip.io

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

185.203.18.220:443 href · ×4
185.151.51.53:80 href · ×2
144.76.174.123:443 href · ×2
3.35.154.64:443 href · ×2
195.26.126.118:8888 href · ×2
52.79.38.143:443 href · ×2
51.79.192.119:443 href · ×1
100.28.99.173:80 href · ×1
50.112.182.97:443 href · ×1
139.99.39.162:443 href · ×1
34.192.6.68:80 href · ×1
52.6.112.150:443 href · ×1
200.19.215.176:443 href · ×1
45.115.154.45:80 href · ×1
15.165.125.212:443 href · ×1
44.225.153.18:443 href · ×1
199.91.65.83:443 href · ×1
62.153.168.74:80 href · ×1
95.142.43.70:8443 href · ×1
165.227.237.143:443 href · ×1
184.32.11.103:443 href · ×1
185.224.197.42:443 href · ×1
52.192.183.189:443 href · ×1
103.95.166.67:80 href · ×1
103.147.199.123:80 href · ×1
20.211.239.25:80 href · ×1
208.52.32.14:80 href · ×1
81.229.250.89:80 href · ×1
96.231.233.54:80 href · ×1
199.255.96.221:80 href · ×1
51.79.197.128:443 href · ×1
62.153.168.74:443 href · ×1
103.16.160.108:443 href · ×1
51.79.193.162:443 href · ×1
32.184.78.193:443 href · ×1
51.79.192.122:443 href · ×1
72.167.84.60:443 href · ×1
139.99.116.69:443 href · ×1
43.166.253.58:443 href · ×1
15.235.142.42:443 href · ×1
81.229.250.89:443 href · ×1
223.235.64.190:80 href · ×1
103.163.125.232:80 href · ×1
103.134.117.15:80 href · ×1
139.99.54.196:443 href · ×1
51.140.107.112:8088 href · ×1

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-cloud-e2.googledomains.com 2026-05-25 22:11:29.484 2026-07-28 19:39:40.097
AAAA 2600:1901:0:b2bd:: 2026-05-25 22:11:29.484 2026-07-28 19:39:40.097
NS ns-cloud-e4.googledomains.com 2026-05-25 22:11:29.484 2026-07-28 19:39:40.097
NS ns-cloud-e1.googledomains.com 2026-05-25 22:11:29.484 2026-07-28 19:39:40.097
A 34.160.111.145 2026-05-25 22:11:29.484 2026-07-28 19:39:40.097
NS ns-cloud-e3.googledomains.com 2026-05-25 22:11:29.484 2026-07-28 19:39:40.097