Check-Host.cc

Domain

ns.adobe.com

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

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

DNS Records

A
AAAA
MX
NS
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.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

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

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

181.111.241.85:80 href · ×27
203.67.131.79:80 href · ×26
80.11.53.220:80 href · ×16
59.124.230.167:80 href · ×13
1.34.75.105:80 href · ×13
61.216.150.81:80 href · ×13
203.70.11.152:80 href · ×13
218.32.75.101:80 href · ×13
203.70.11.141:80 href · ×13
59.124.230.166:80 href · ×13
59.120.2.73:80 href · ×13
61.219.188.248:8080 href · ×13
203.70.11.157:80 href · ×13
220.130.144.171:8080 href · ×13
116.206.104.35:443 href · ×12
116.206.104.35:80 href · ×12
64.227.34.192:80 href · ×10
188.166.106.4:443 href · ×10
34.236.125.232:443 href · ×9
181.111.241.85:443 href · ×9
39.107.90.23:80 href · ×8
64.64.6.57:443 href · ×7
31.207.36.94:443 href · ×6
20.91.212.242:80 href · ×5
148.69.180.233:443 href · ×4
168.138.144.100:80 href · ×4
94.53.249.49:443 href · ×4
51.107.177.144:443 href · ×4
52.18.235.91:443 href · ×4
99.80.58.113:443 href · ×4
8.155.7.101:8088 href · ×4
111.90.148.199:443 href · ×4
148.69.180.226:443 href · ×4
35.182.180.103:80 href · ×4
35.190.15.229:80 href · ×4
47.92.208.80:443 href · ×4
128.140.104.92:443 href · ×3
160.153.47.61:443 href · ×3
45.162.170.49:443 href · ×3
172.104.239.80:80 href · ×2
94.23.26.190:443 href · ×2
157.245.34.6:443 href · ×2
160.153.248.164:443 href · ×2
34.226.28.133:443 href · ×2
54.149.139.115:443 href · ×2
213.183.189.68:443 href · ×2
23.254.228.247:443 href · ×1
52.177.143.174:443 href · ×1
133.130.79.188:80 href · ×1
193.239.1.94:80 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-b1.googledomains.com 2026-05-26 00:03:35.658 2026-07-24 04:28:24.806
NS ns-cloud-b3.googledomains.com 2026-05-26 00:03:35.658 2026-07-24 04:28:24.806
NS ns-cloud-b2.googledomains.com 2026-05-26 00:03:35.658 2026-07-24 04:28:24.806
NS ns-cloud-b4.googledomains.com 2026-05-26 00:03:35.658 2026-07-24 04:28:24.806