Skip to content

Hostname

t2.sa

Last fetched

t2.sa resolves to 8.213.82.126, announced in 8.213.64.0/18 by ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. in SA. t2.sa 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 · t2.saRouting diversity1.5/10Peering density7.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.5/10canon.whisper.security/host/t2.sa

Resolution chain

IPv6 resolution

No AAAA record for t2.sa is recorded in WhisperGraph.

Attribution

hangzhou alibaba advertising

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for t2.sa. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

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

  • ns1.cloudns.net
  • pns1.cloudns.net
  • pns3.cloudns.net
  • pns4.cloudns.net
  • pns5.cloudns.net
  • 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

  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • mail.t2.sa

SPF policy

  • ip: 8.213.39.156/32
  • ip: 8.213.33.192/32
  • ip: 95.177.193.211/32
  • include: amazonses.com
  • include: _spf.google.com
  • include: rp.oracleemaildelivery.com
  • a: email.sogolytics.com
  • a: jed-mail.rich.sa
  • a: mail.t2.sa

Threat-feed evidence

History

Related pages

Pivot from t2.sa 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: "t2.sa"})-[: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.