Skip to content

Hostname

thingstream.io

Last fetched

thingstream.io resolves to 108.138.7.107, announced in 108.138.0.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. thingstream.io 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 · thingstream.ioRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.6/10canon.whisper.security/host/thingstream.io

Resolution chain

IPv6 resolution

No AAAA record for thingstream.io is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
thingstream

Subdomains

Subdomain
auth.thingstream.io
developer.thingstream.io
info.thingstream.io
intranet.thingstream.io
l.thingstream.io
logs-stage.thingstream.io
logs.thingstream.io
mail2.thingstream.io
modem-map.thingstream.io
portal.thingstream.io
status.thingstream.io
support.thingstream.io

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

Mail and authentication

Nameservers

  • ns-500.awsdns-62.com
  • ns-604.awsdns-11.net
  • ns-1452.awsdns-53.org
  • ns-1971.awsdns-54.co.uk

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: amazonses.com
  • include: email.chargebee.com
  • include: _spf.google.com
  • include: _spf.sparkpostmail.com
  • include: mail.zendesk.com
  • include: 4608947.spf03.hubspotemail.net

Threat-feed evidence

History

Related pages

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