Check-Host.cc

Domain

nextjs.org

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

Run a live full scan of nextjs.org

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

DNS Records

A
216.230.84.1, 216.230.84.129, 216.230.84.193, 216.230.84.65, 216.230.86.1, 216.230.86.129, 216.230.86.193, 216.230.86.65
AAAA
MX
1 aspmx.l.google.com, 10 alt3.aspmx.l.google.com, 10 alt4.aspmx.l.google.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
ns1.vercel-dns.com, ns2.vercel-dns.com
TXT
google-site-verification=BsXDDAvxM3KYqCMD-vaPIxduP9YLqllhaBlERyhjsgw, google-site-verification=VUelRm0rDJ9Mxpi3RYfJ0M_Qqbxyo8mSYdn0grLEFIU, google-site-verification=h7m7xPSl46-ALWigMUJfFFOFZjKe3jZECHyXSomzXvM, google-site-verification=roTfUbzRkjTgiiXb6Lbsh2sQyaAlS_sN32t5nMz8kTQ, v=spf1 include:_spf.google.com include:servers.mcsv.net include:sendgrid.net ~all
CNAME
CAA
0 issue "letsencrypt.org", 0 issue "pki.goog", 0 issue "sectigo.com"

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
nextjs.org 2026-07-28 19:02:52.609
www.nextjs.org 2026-07-19 17:15:05.667

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.

146.56.108.71:443 href · ×66
144.24.71.167:443 href · ×33
83.29.29.229:8081 href · ×16
13.213.37.164:443 href · ×6
128.184.235.242:443 href · ×6
157.180.125.133:443 href · ×6
52.166.230.61:443 href · ×6
51.136.84.141:80 href · ×6
124.220.7.99:443 href · ×6
138.199.223.33:443 href · ×6
173.249.21.131:80 href · ×6
34.111.145.44:443 href · ×6
4.182.224.6:80 href · ×6
13.125.64.7:80 href · ×6
47.96.250.132:443 href · ×6
134.209.153.187:443 href · ×6
110.42.209.86:8081 href · ×6
65.99.225.87:80 href · ×4
39.98.46.122:443 href · ×4
188.166.214.154:443 href · ×4
178.128.20.137:443 href · ×4
69.58.56.119:443 href · ×4
106.55.43.118:80 href · ×4
91.228.155.252:443 href · ×4
104.236.74.164:443 href · ×4
80.241.220.188:80 href · ×4
108.175.9.82:80 href · ×4
95.163.220.246:443 href · ×4
43.204.122.38:443 href · ×4
83.147.37.90:443 href · ×4
95.179.245.99:443 href · ×4
91.219.239.224:80 href · ×4
45.190.176.59:80 href · ×4
106.55.43.118:443 href · ×4
49.247.139.24:80 href · ×4
167.99.152.246:80 href · ×4
162.43.4.195:443 href · ×4
8.134.137.133:80 href · ×4
46.62.175.62:443 href · ×4
116.198.241.110:80 href · ×4
194.233.65.233:443 href · ×4
20.6.36.97:443 href · ×4
103.197.189.0:80 href · ×4
165.227.153.181:80 href · ×4
82.165.132.27:80 href · ×4
159.198.42.40:8088 href · ×4
77.95.0.84:443 href · ×4
173.62.120.199:443 href · ×4
167.235.141.143:443 href · ×4
206.189.191.38:443 href · ×4

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
TXT google-site-verification=BsXDDAvxM3KYqCMD-vaPIxduP9YLqllhaBlERyhjsgw 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
TXT google-site-verification=roTfUbzRkjTgiiXb6Lbsh2sQyaAlS_sN32t5nMz8kTQ 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
TXT google-site-verification=h7m7xPSl46-ALWigMUJfFFOFZjKe3jZECHyXSomzXvM 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
A 216.230.86.193 2026-05-25 22:07:29.493 2026-06-04 23:51:53.290
NS ns1.vercel-dns.com 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
TXT v=spf1 include:_spf.google.com include:servers.mcsv.net include:sendgrid.net ~all 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
MX 5 alt2.aspmx.l.google.com 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
MX 10 alt4.aspmx.l.google.com 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
MX 1 aspmx.l.google.com 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
MX 5 alt1.aspmx.l.google.com 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
TXT google-site-verification=VUelRm0rDJ9Mxpi3RYfJ0M_Qqbxyo8mSYdn0grLEFIU 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
MX 10 alt3.aspmx.l.google.com 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
NS ns2.vercel-dns.com 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
A 216.230.86.1 2026-05-25 22:07:29.493 2026-07-28 19:02:52.609
A 216.230.86.65 2026-05-25 22:09:29.497 2026-05-31 07:17:40.825
A 216.230.84.1 2026-05-25 22:09:29.497 2026-06-04 23:51:53.290
CAA 0 issue "sectigo.com" 2026-05-26 02:30:04.450 2026-07-28 19:02:52.609
A 216.230.86.129 2026-05-26 02:30:04.450 2026-05-27 21:37:40.771
CAA 0 issue "pki.goog" 2026-05-26 02:30:04.450 2026-07-28 19:02:52.609
CAA 0 issue "letsencrypt.org" 2026-05-26 02:30:04.450 2026-07-28 19:02:52.609
A 216.230.84.193 2026-05-26 03:23:54.879 2026-05-27 11:25:54.013
A 216.230.84.65 2026-05-26 08:15:11.123 2026-05-27 19:07:40.763
A 216.230.84.129 2026-05-26 08:15:11.123 2026-05-31 07:17:40.825