Check-Host.cc

Domain

api.qrserver.com

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

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

DNS Records

A
159.69.246.187, 195.201.128.178, 88.99.85.235, 95.216.163.127
AAAA
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.

3.11.221.141:443 href · ×269
78.47.152.204:443 href · ×30
168.76.210.221:443 href · ×16
168.76.211.222:443 href · ×16
47.121.116.95:80 href · ×12
154.201.187.78:443 href · ×11
154.201.206.195:443 href · ×11
154.201.187.79:443 href · ×11
154.201.232.29:443 href · ×11
154.201.200.24:443 href · ×11
154.201.187.93:443 href · ×11
160.124.225.62:443 href · ×11
154.201.187.76:443 href · ×11
154.201.235.71:443 href · ×11
154.201.200.6:443 href · ×11
154.201.203.102:443 href · ×11
154.201.235.79:443 href · ×11
160.124.225.36:443 href · ×11
154.201.232.4:443 href · ×11
154.201.203.99:443 href · ×11
160.124.225.40:443 href · ×11
160.124.225.52:443 href · ×11
122.51.234.75:443 href · ×10
47.100.125.85:443 href · ×10
178.128.31.226:443 href · ×9
168.76.210.212:443 href · ×8
168.76.210.202:443 href · ×8
168.76.212.210:443 href · ×8
168.76.212.214:443 href · ×8
168.76.210.216:443 href · ×8
168.76.212.208:443 href · ×8
168.76.215.218:443 href · ×8
168.76.211.211:443 href · ×8
168.76.212.199:443 href · ×8
14.225.192.149:443 href · ×8
168.76.213.198:443 href · ×8
168.76.215.221:443 href · ×8
168.76.217.219:443 href · ×8
168.76.216.204:443 href · ×8
168.76.215.213:443 href · ×8
168.76.213.214:443 href · ×8
168.76.215.196:443 href · ×8
168.76.210.208:443 href · ×8
168.76.211.205:443 href · ×8
168.76.211.195:443 href · ×8
168.76.213.222:443 href · ×8
168.76.213.196:443 href · ×8
168.76.217.194:443 href · ×8
168.76.212.195:443 href · ×8
168.76.211.216:443 href · ×8

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
A 95.216.163.127 2026-05-25 21:56:50.553 2026-07-28 19:57:26.855
A 159.69.246.187 2026-05-25 21:56:50.553 2026-07-28 19:57:26.855
A 88.99.85.235 2026-05-25 21:56:50.553 2026-07-28 19:57:26.855
A 195.201.128.178 2026-05-25 21:56:50.553 2026-07-28 19:57:26.855