Skip to content

Hostname

teamliquid.net

Last fetched

teamliquid.net resolves to 144.217.237.0, announced in 144.217.0.0/16 by OVH - OVH SAS in CA. teamliquid.net is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · teamliquid.netRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/teamliquid.net

Resolution chain

IPv6 resolution

Attribution

ovh

ORIGIN_AS

WHOIS identity

Registrar
iana:1910
Registrant organisation
liquid enterprises b.v.
Contact emails
47eca8552f754f759560aeaf1a04bb60.protect@whoisguard.com, 8080f4185ddd44d78a822daf555a5e49.protect@whoisguard.com, accounts@teamliquid.net, 88a373a06572d011c9494f7eeffddbbb-19412425@contact.gandi.net

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • fay.ns.cloudflare.com
  • lee.ns.cloudflare.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf0.teamliquid.net
  • ip: 135.125.108.175
  • ip: 135.125.87.180
  • ip: 144.217.237.6
  • ip: 144.217.237.7
  • ip: 2001:41d0:1008:1258:0:0:0:1
  • ip: 51.255.70.88
  • ip: 95.216.116.145

Threat-feed evidence

History

Related pages

Pivot from teamliquid.net into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

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

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