Skip to content

Hostname

teams.microsoft.net

Last fetched

teams.microsoft.net appears in WhisperGraph with partial WHOIS records but no current public IPv4 resolution.

Nutrition Label

WHISPER CANON · teams.microsoft.netRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/teams.microsoft.net

Resolution chain

teams.microsoft.net has no current public IPv4 resolution in WhisperGraph. The WHOIS record below is the only graph data we have on this hostname.

WHOIS identity

No WHOIS records are currently associated with teams.microsoft.net in WhisperGraph.

Subdomains

48 observed subdomains of teams.microsoft.net.

Subdomain
admin-dev.teams.microsoft.net
trouter-int.teams.microsoft.net
tgs.teams.microsoft.net
teamsgraph.teams.microsoft.net
relay.teams.microsoft.net
records.teams.microsoft.net
recommend.teams.microsoft.net
presence.teams.microsoft.net
pma.teams.microsoft.net
minimalcosmicservice.teams.microsoft.net
mcr.teams.microsoft.net
mailhook.teams.microsoft.net
int.teams.microsoft.net
infra.teams.microsoft.net
dna.teams.microsoft.net
dialin.teams.microsoft.net
cqd.teams.microsoft.net
cpcapi-int.teams.microsoft.net
cpcapi-dev.teams.microsoft.net
bmc.teams.microsoft.net
attend.teams.microsoft.net
analytics-int.teams.microsoft.net
admin-local.teams.microsoft.net
admin-int.teams.microsoft.net

Showing 24 of 48. View all subdomains →

Threat posture

History

Related pages

Pivot deeper into the graph from teams.microsoft.net.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "teams.microsoft.net"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.