Check-Host.cc

Domain

blog.openresty.com

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

Run a live full scan of blog.openresty.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
2
in our scans

DNS Records

A
13.52.62.164, 13.59.70.33, 3.74.86.167, 35.177.193.218, 54.219.222.148
AAAA
2a05:d014:808:3600:d7c8:720c:b584:cdeb
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.

160.124.206.254:80 href · ×18
162.250.190.232:80 href · ×18
23.224.70.109:80 href · ×18
154.23.199.84:80 href · ×18
164.52.71.217:443 href · ×18
154.23.205.63:80 href · ×18
140.245.127.202:443 href · ×18
76.223.24.88:80 href · ×18
154.210.252.172:80 href · ×15
111.48.120.143:80 href · ×15
172.234.107.97:80 href · ×15
207.57.189.240:80 href · ×15
207.90.253.38:80 href · ×15
140.84.178.238:80 href · ×12
152.42.143.166:80 href · ×12
199.96.133.42:80 href · ×12
58.84.58.15:80 href · ×12
164.52.57.81:443 href · ×12
47.254.121.65:443 href · ×12
160.124.215.167:81 href · ×12
202.124.248.131:80 href · ×12
188.166.40.231:80 href · ×12
154.23.202.81:80 href · ×12
113.45.149.201:80 href · ×12
8.209.102.234:443 href · ×12
138.197.92.82:80 href · ×12
39.98.122.44:443 href · ×12
8.147.114.4:80 href · ×12
148.153.225.126:443 href · ×12
192.253.235.31:80 href · ×12
124.156.125.85:443 href · ×12
23.82.32.215:80 href · ×12
43.138.118.61:80 href · ×12
154.12.53.22:80 href · ×12
164.52.57.236:443 href · ×12
42.117.9.131:80 href · ×12
34.149.73.220:443 href · ×12
121.41.17.214:8080 href · ×12
101.132.43.77:80 href · ×12
27.50.63.70:80 href · ×12
154.213.115.231:81 href · ×12
152.42.132.76:80 href · ×12
91.246.39.27:80 href · ×12
104.236.11.22:80 href · ×12
157.245.65.37:80 href · ×12
23.94.225.35:80 href · ×12
82.157.22.243:443 href · ×12
139.159.243.62:443 href · ×12
45.78.224.119:443 href · ×12
220.197.54.106:443 href · ×12

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
AAAA 2a05:d014:808:3600:d7c8:720c:b584:cdeb 2026-05-25 21:56:50.553 2026-07-28 20:58:16.328
A 3.74.86.167 2026-05-25 21:56:50.553 2026-07-28 20:58:16.328
A 13.59.70.33 2026-06-14 22:52:09.672 2026-07-28 19:48:54.308
A 13.52.62.164 2026-06-15 02:27:57.086 2026-07-28 10:19:39.346
A 54.219.222.148 2026-06-15 02:27:57.086 2026-07-28 10:19:39.346
A 35.177.193.218 2026-06-15 09:04:06.082 2026-06-17 11:42:04.291