Skip to content

Hostname

motivosity.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
zc2gb9n33h9@networksolutionsprivateregistration.com

Subdomains

Subdomain
abc.motivosity.com
app.motivosity.com
asea.motivosity.com
blog.motivosity.com
get.motivosity.com
hancockhealth.motivosity.com
healthequity.motivosity.com
help.motivosity.com
images.motivosity.com
insight.motivosity.com
mystanns.motivosity.com
ndp.motivosity.com

Showing 12 of 20. 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-350.awsdns-43.com
  • ns-995.awsdns-60.net
  • ns-1209.awsdns-23.org
  • ns-1657.awsdns-15.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • ms25589236.msv1.invalid

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: spf.intercom-mail.com
  • include: spf.hubspotemail.net

Threat-feed evidence

History

Related pages

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