Skip to content

Hostname

hr4.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
bernard lechler
Contact emails
administrator@theminery.com, 07cf09b0-2b2c-42d6-aafc-46e7e123f362@identity-protect.org, 126034fb-6502-4153-8fe4-039524be06ff@identity-protect.org, 3dfda8ce-aaf3-4c69-a5d3-4b5952318072@identity-protect.org, a56222e4-9189-4a27-ba2f-e6e5c1cad922@identity-protect.org, afa560e6-14c1-4549-8a72-54b4cf8737a1@identity-protect.org, owner-2011439@hr4.com.whoisprivacyservice.org, owner-2031758@hr4.com.whoisprivacyservice.org, owner-4476865@hr4.com.whoisprivacyservice.org, owner-5183187@hr4.com.whoisprivacyservice.org, owner-5629071@hr4.com.whoisprivacyservice.org, owner-5701638@hr4.com.whoisprivacyservice.org, owner@hr4.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-406.awsdns-50.com
  • ns-1002.awsdns-61.net
  • ns-1412.awsdns-48.org
  • ns-1725.awsdns-23.co.uk

MX records

  • hr4-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: 3463348.spf01.hubspotemail.net

Threat-feed evidence

History

Related pages

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