Skip to content

Hostname

refinementservices.com

Last fetched

refinementservices.com resolves to 18.205.140.230, announced in 18.204.0.0/14 by AMAZON-AES - Amazon.com, Inc. in US. 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 · refinementservices.comRouting diversity2.4/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/refinementservices.com

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
neil.kugelman@gmail.com, 4518191e-58ed-480b-95c9-e77487e72635@identity-protect.org, ea47b101-cc71-406d-a468-cceec6f13560@identity-protect.org, f3089727-eaaa-48f1-9cab-9ddbfe90f792@identity-protect.org

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

  • ns-214.awsdns-26.com
  • albert.ns.cloudflare.com
  • josephine.ns.cloudflare.com
  • ns-697.awsdns-23.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
  • 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 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: "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.