Skip to content

Hostname

launch.refinementservices.com

Last fetched

launch.refinementservices.com resolves to 34.192.91.98, announced in 34.192.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. launch.refinementservices.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 · launch.refinementservices.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/launch.refinementservices.com

Resolution chain

IPv6 resolution

No AAAA record for launch.refinementservices.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for launch.refinementservices.com. 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.

Mail and authentication

Nameservers

  • ns-214.awsdns-26.com
  • ns-697.awsdns-23.net
  • ns-1031.awsdns-00.org
  • ns-1897.awsdns-45.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.atlassian.net

Threat-feed evidence

History

Related pages

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