Skip to content

Hostname

researchbods.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
robmhilton@gmail.com, 072da304-ce37-4952-8174-fe2c1e040323@identity-protect.org, 09660b66-361e-4c7d-b8f9-ab8b96cbfc8e@identity-protect.org, 5c508947-e949-4b18-ab5e-bcd2c091c721@identity-protect.org, 83f9db3e-209a-4e79-860b-1c7b3c42c8e3@identity-protect.org, 8ec28a51-8d8d-4d18-be61-15964a52d199@identity-protect.org, ab295d13-5e60-48ec-9749-ccb3ac893be7@identity-protect.org, c9616911-b7c1-4138-aac7-3296692bf995@identity-protect.org, owner-93245@researchbods.com.whoisprivacyservice.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-491.awsdns-61.com
  • ns-532.awsdns-02.net
  • ns-1350.awsdns-40.org
  • ns-1820.awsdns-35.co.uk

MX records

  • eu-smtp-inbound-1.mimecast.com
  • eu-smtp-inbound-2.mimecast.com

SPF policy

  • include: amazonses.com
  • include: eu._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: 9492080.spf05.hubspotemail.net
  • include: spf.uk.signature365.net

Threat-feed evidence

History

Related pages

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