Check-Host.cc

Domain

team.badoo.com

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

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

DNS Records

A
31.222.67.112
AAAA
MX
10 ASPMX.L.GOOGLE.com, 10 aspmx.l.google.com, 20 ALT1.ASPMX.L.GOOGLE.com, 20 ALT2.ASPMX.L.GOOGLE.com, 20 alt1.aspmx.l.google.com, 20 alt2.aspmx.l.google.com, 30 ASPMX2.GOOGLEMAIL.com, 30 ASPMX3.GOOGLEMAIL.com
NS
TXT
apple-domain-verification=zByEysKz3jsXdrl0, miro-verification=08fe6cc0409ef192114873c32c66f2e84643bec0, v=spf1 include:_spf.google.com ip4:31.222.64.0/20 ip4:159.253.176.0/21 ip4:37.58.26.136/29 ip4:217.138.10.24/29 ip4:65.123.29.208/28 -all
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.

209.97.181.200:443 href · ×1
178.62.207.140:443 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
A 31.222.67.112 2026-06-14 22:23:29.853 2026-06-14 23:22:00.742
TXT v=spf1 include:_spf.google.com ip4:31.222.64.0/20 ip4:159.253.176.0/21 ip4:37.58.26.136/29 ip4:217.138.10.24/29 ip4:65.123.29.208/28 -all 2026-06-14 22:23:29.853 2026-06-14 23:22:00.742
MX 30 ASPMX3.GOOGLEMAIL.com 2026-06-14 22:23:29.853 2026-06-14 22:23:29.853
MX 10 ASPMX.L.GOOGLE.com 2026-06-14 22:23:29.853 2026-06-14 22:23:29.853
TXT apple-domain-verification=zByEysKz3jsXdrl0 2026-06-14 22:23:29.853 2026-06-14 23:22:00.742
MX 30 ASPMX2.GOOGLEMAIL.com 2026-06-14 22:23:29.853 2026-06-14 22:23:29.853
MX 20 ALT1.ASPMX.L.GOOGLE.com 2026-06-14 22:23:29.853 2026-06-14 22:23:29.853
MX 20 ALT2.ASPMX.L.GOOGLE.com 2026-06-14 22:23:29.853 2026-06-14 22:23:29.853
TXT miro-verification=08fe6cc0409ef192114873c32c66f2e84643bec0 2026-06-14 22:23:29.853 2026-06-14 23:22:00.742
MX 20 alt1.aspmx.l.google.com 2026-06-14 23:22:00.742 2026-06-14 23:22:00.742
MX 30 aspmx2.googlemail.com 2026-06-14 23:22:00.742 2026-06-14 23:22:00.742
MX 20 alt2.aspmx.l.google.com 2026-06-14 23:22:00.742 2026-06-14 23:22:00.742
MX 10 aspmx.l.google.com 2026-06-14 23:22:00.742 2026-06-14 23:22:00.742
MX 30 aspmx3.googlemail.com 2026-06-14 23:22:00.742 2026-06-14 23:22:00.742