Check-Host.cc

Domain

2.team

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

Run a live full scan of 2.team

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

DNS Records

A
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

Subject: khmail2.teamrise.com.tw
Issuer: YR1
SANs: khmail2.teamrise.com.tw
Subject: web2.teamxstream.com
Issuer: R12
SANs: web2.teamxstream.com
Subject: lankershim2.teamaspect.com
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: lankershim2.teamaspect.com, www.lankershim2.teamaspect.com
Subject: avayarw2.teamaccess.tsys.com
Issuer: Sectigo Public Server Authentication CA OV R36
SANs: avayarw2.teamaccess.tsys.com, tcc-aads.teamaccess.tsys.com, tcc-ixsettings.teamaccess.tsys.com, tcc-rw1.teamaccess.tsys.com, tcc-rw2.teamaccess.tsys.com, tcc-weblm.teamaccess.tsys.com, www.avayarw2.teamaccess.tsys.com
Subject: tm2test2.teamcore.net
Issuer: WR3
SANs: tm2test2.teamcore.net
Subject: host2.teamcloud.am
Issuer: host2.teamcloud.am
SANs: host2.teamcloud.am
Subject: 1x2.team
Issuer: YE1
SANs: 1x2.team
Subject: tlgames.ex2.team
Issuer: YR2
SANs: tlgames.ex2.team
Subject: host2.teamcloud.am
Issuer: host2.teamcloud.am
SANs: host2.teamcloud.am
Subject: *.aws-922360040172.team-lab.com
Issuer: Amazon RSA 2048 M01
SANs: *.aws-922360040172.team-lab.com
Subject: *.aws-922360040172.team-lab.com
Issuer: Amazon RSA 2048 M02
SANs: *.aws-922360040172.team-lab.com
Subject: *.na2.teamsupport.com
Issuer: Amazon RSA 2048 M01
SANs: *.na2.teamsupport.com
Subject: dev2.teamtag.works
Issuer: Amazon ECDSA 256 M04
SANs: dev2.teamtag.works
Subject: webapps2022.teampenta.com
Issuer: YR2
SANs: webapps2022.teampenta.com
Subject: host2.teamcloud.am
Issuer: host2.teamcloud.am
SANs: host2.teamcloud.am
Subject: eurekamath2.teamcamelot.com
Issuer: E7
SANs: eurekamath2.teamcamelot.com, nyspolice2.teamcamelot.com
Subject: host2.teamcloud.am
Issuer: host2.teamcloud.am
SANs: host2.teamcloud.am
Subject: soap.grantee2.teams.simpler.grants.gov
Issuer: HydrantID Server CA O1
SANs: soap.grantee2.teams.simpler.grants.gov
Subject: v2.teamlens.co
Issuer: E7
SANs: v2.teamlens.co
Subject: *.aws-922360040172.team-lab.com
Issuer: Amazon RSA 2048 M01
SANs: *.aws-922360040172.team-lab.com
Subject: *.prod2.teams-api.anywhere.re
Issuer: Amazon RSA 2048 M02
SANs: *.prod2.teams-api.anywhere.re
Subject: *.aws-922360040172.team-lab.com
Issuer: Amazon RSA 2048 M01
SANs: *.aws-922360040172.team-lab.com
Subject: ns2.teamcloud.am
Issuer: YR1
SANs: ns2.teamcloud.am
Subject: message1.pr-dhi02.teams.spectrocloud.com
Issuer: SpectroCloud CA
SANs: *.message1.pr-dhi02.teams.spectrocloud.com, message1.pr-dhi02.teams.spectrocloud.com
Subject: *.na2.teamsupport.com
Issuer: Amazon RSA 2048 M04
SANs: *.na2.teamsupport.com
Subject: mcp-v2.team.trabian.ai
Issuer: Amazon RSA 2048 M04
SANs: mcp-v2.team.trabian.ai
Subject: *.y2.team
Issuer: Amazon RSA 2048 M03
SANs: *.y2.team, y2.team
Subject: *.aws-922360040172.team-lab.com
Issuer: Amazon RSA 2048 M03
SANs: *.aws-922360040172.team-lab.com
Subject: *.klo2.teams-api.anywhere.re
Issuer: Amazon RSA 2048 M04
SANs: *.klo2.teams-api.anywhere.re
Subject: *.na2.teamsupport.com
Issuer: Amazon RSA 2048 M04
SANs: *.na2.teamsupport.com

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

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

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.