Skip to content

Hostname

betterimpactmail.com

Last fetched

betterimpactmail.com resolves to 209.15.205.181, announced in 209.15.192.0/18 by COGECO-PEER1 - Aptum Technologies in CA. betterimpactmail.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 · betterimpactmail.comRouting diversity1.5/10Peering density6.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.0/10canon.whisper.security/host/betterimpactmail.com

Resolution chain

IPv6 resolution

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

Attribution

aptum

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
better impact
Contact emails
tony@betterimpact.com

Subdomains

Subdomain
mta-sts.betterimpactmail.com
www.betterimpactmail.com

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns1.betterimpact.com
  • ns2.betterimpact.com
  • ns3.betterimpact.com
  • ns4.betterimpact.com
  • ns5.betterimpact.com
  • ns6.betterimpact.com
  • uz5c0c3s8l2rl9wzv47ju3fxnk8l4ly0r56j888sg6nqrmy0db4mn2.b.ast.ns.buddyns.com
  • uz5c0c3s8l2rl9wzv47ju3fxnk8l4ly0r56j888sg6nqrmy0db4mn2.c.ast.ns.buddyns.com
  • uz5c0c3s8l2rl9wzv47ju3fxnk8l4ly0r56j888sg6nqrmy0db4mn2.d.ast.ns.buddyns.com
  • 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

MX records

  • mx1.volunteer2mail.com

SPF policy

  • ip: 209.15.205.180/32
  • ip: 209.15.205.182/32
  • ip: 198.21.7.99/32

Threat-feed evidence

History

Related pages

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