Check-Host.cc

Domain

open.er-api.com

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

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

DNS Records

A
104.26.4.5, 104.26.5.5, 172.67.70.147
AAAA
2606:4700:20::681a:405, 2606:4700:20::681a:505, 2606:4700:20::ac43:4693
MX
NS
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.

68.183.215.91:443 href · ×2
154.17.24.69:443 href · ×2
137.175.57.6:80 href · ×2
144.24.112.151:443 href · ×2
103.106.228.217:443 href · ×2
137.175.57.117:80 href · ×2
178.105.200.39:80 href · ×2
47.95.111.150:80 href · ×1
192.227.237.31:443 href · ×1
220.117.167.126:80 href · ×1
172.104.191.172:443 href · ×1
192.129.191.204:443 href · ×1
219.117.224.185:443 href · ×1
111.119.243.80:80 href · ×1
168.144.30.143:443 href · ×1
158.180.91.38:443 href · ×1
172.105.74.157:443 href · ×1
46.107.158.204:443 href · ×1
45.8.112.196:8443 href · ×1
121.180.81.42:8000 href · ×1
167.148.203.245:8008 href · ×1
77.110.122.237:80 href · ×1
38.123.103.21:8080 href · ×1
47.100.170.196:80 href · ×1
168.107.28.53:80 href · ×1
5.104.85.235:443 href · ×1
85.235.64.16:443 href · ×1
152.42.163.150:80 href · ×1
51.178.25.190:443 href · ×1
77.110.122.237:443 href · ×1
107.174.81.80:443 href · ×1
185.244.144.148:443 href · ×1
147.45.251.106:80 href · ×1
78.17.46.136:80 href · ×1
213.202.255.38:443 href · ×1
89.124.110.25:443 href · ×1
38.123.103.21:80 href · ×1
47.102.121.209:443 href · ×1
118.89.83.139:443 href · ×1
193.29.56.19:443 href · ×1
192.210.187.91:443 href · ×1
8.211.154.175:443 href · ×1
193.134.250.232:443 href · ×1
155.103.67.105:443 href · ×1
118.145.101.252:443 href · ×1
34.83.2.126:5000 href · ×1
51.83.32.199:80 href · ×1
37.27.219.137:443 href · ×1
195.248.242.127:80 href · ×1
18.216.154.114: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

Domain timeline pending

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