Skip to content

Hostname

teamgram.com

Last fetched

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

Resolution chain

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
******** ******** (see notes section below on how to view unmasked data)
Contact emails
********@*****.***, domreg@bodru.com, domreg@yureklis.com, ayurekli@alumni.stanford.edu

Subdomains

Subdomain
ads-mcp.teamgram.com
blg1.teamgram.com
blg2.teamgram.com
blogs.teamgram.com
cm.teamgram.com
cmsx.teamgram.com
flow.teamgram.com
form.teamgram.com
kb1.teamgram.com
sprt2.teamgram.com
stage-892.teamgram.com
support.teamgram.com

Showing 12 of 14. 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-123.awsdns-15.com
  • ns-721.awsdns-26.net
  • ns-1299.awsdns-34.org
  • ns-1939.awsdns-50.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: amazonses.com
  • include: _spf.google.com
  • include: _spf.mlsend.com
  • include: servers.mcsv.net
  • include: mailgun.org

Threat-feed evidence

History

Related pages

Pivot from teamgram.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: "teamgram.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.