Check-Host.cc

Domain

cmp.gatekeeperconsent.com

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

Run a live full scan of cmp.gatekeeperconsent.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
5
in our scans

DNS Records

A
104.21.42.32, 172.67.199.186
AAAA
2606:4700:3030::6815:2a20, 2606:4700:3031::ac43:c7ba, 2606:4700:3033::ac43:c7ba, 2606:4700:3035::6815:2a20
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.

89.44.139.193:443 href · ×3
148.113.202.95:8080 href · ×2
154.83.148.142:443 href · ×2
135.148.190.169:8080 href · ×2
157.180.30.22:443 href · ×2
43.156.7.173:80 href · ×2
43.133.226.68:443 href · ×2
209.74.89.49:443 href · ×2
35.161.126.15:443 href · ×1
35.205.131.35:443 href · ×1
50.112.251.5:443 href · ×1
111.230.109.26:443 href · ×1
46.101.199.78:8080 href · ×1
15.197.69.133:443 href · ×1
54.39.16.114:443 href · ×1
2.26.73.128:443 href · ×1
34.29.79.75:80 href · ×1
159.89.166.241:443 href · ×1
172.245.68.67:443 href · ×1
44.209.16.235:443 href · ×1
68.178.202.104:80 href · ×1
142.93.206.111:443 href · ×1
52.55.232.47:443 href · ×1
104.248.51.70:443 href · ×1
82.208.22.215:443 href · ×1
49.51.194.176:80 href · ×1
66.116.196.86:443 href · ×1
52.71.240.184:443 href · ×1
44.223.205.99:443 href · ×1
64.227.80.92:80 href · ×1
37.27.110.179:443 href · ×1
103.171.76.62:80 href · ×1
3.121.247.52:443 href · ×1
3.234.121.144:443 href · ×1
146.190.42.36:443 href · ×1
199.192.29.66:443 href · ×1
3.128.53.208:443 href · ×1
73.159.58.18:443 href · ×1
66.29.130.58:8000 href · ×1
3.221.244.187:443 href · ×1
68.178.202.104:81 href · ×1
68.234.48.70:443 href · ×1
188.93.234.16:443 href · ×1
64.23.220.163:443 href · ×1
147.182.141.40:443 href · ×1
128.199.138.217:80 href · ×1
217.154.42.226:80 href · ×1
74.208.125.216:443 href · ×1
132.148.76.247:81 href · ×1
45.56.220.159: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
AAAA 2606:4700:3031::ac43:c7ba 2026-05-26 03:07:47.855 2026-06-17 20:46:23.402
A 172.67.199.186 2026-05-26 03:07:47.855 2026-07-28 13:42:19.007
AAAA 2606:4700:3035::6815:2a20 2026-05-26 03:07:47.855 2026-06-17 20:46:23.402
A 104.21.42.32 2026-05-26 03:07:47.855 2026-07-28 13:42:19.007
AAAA 2606:4700:3030::6815:2a20 2026-06-19 15:07:35.344 2026-07-28 13:42:19.007
AAAA 2606:4700:3033::ac43:c7ba 2026-06-19 15:07:35.344 2026-07-28 13:42:19.007