Skip to content

Hostname

temi.com

Last fetched

temi.com resolves to 100.20.43.234, announced in 100.20.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. temi.com 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 · temi.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/temi.com

Resolution chain

IPv6 resolution

No AAAA record for temi.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
temi.com@domainsbyproxy.com, finance@rev.com

Subdomains

Subdomain
api-feature.temi.com
api.temi.com
auth-dev.temi.com
auth.temi.com
dev.temi.com
feature.temi.com
help.temi.com
stage.temi.com
test.temi.com
www.temi.com

Showing 10 of 17. View all subdomains →

Web-graph footprint

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-220.awsdns-27.com
  • ns-855.awsdns-42.net
  • ns-1244.awsdns-27.org
  • ns-1732.awsdns-24.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: mail.zendesk.com
  • ip: 198.244.49.242
  • ip: 69.72.44.200
  • ip: 69.72.44.216

Threat-feed evidence

History

Related pages

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