Skip to content

Hostname

habby.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
inc. ia consulting
Contact emails
07ac32b4-597d-4bd5-8061-949348de4967@identity-protect.org, 0b08eba6-ed0c-42db-97a3-148f01e9db47@identity-protect.org, 3372a75c-1a2d-4e14-a513-4553af6ecd70@identity-protect.org, 4fa07598-3675-4dee-a916-d88ab60c9ff7@identity-protect.org, 5f99c957-55af-4574-9670-87fa05198161@identity-protect.org, 8bc5fb68-e3d8-4a0d-92e8-fe7aff9502f9@identity-protect.org, owner-2194795@habby.com.whoisprivacyservice.org, owner-2537311@habby.com.whoisprivacyservice.org, owner-2734693@habby.com.whoisprivacyservice.org, owner-322722@habby.com.whoisprivacyservice.org, owner-52773@habby.com.whoisprivacyservice.org, owner-8887412@habby.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-328.awsdns-41.com
  • ns-1014.awsdns-62.net
  • ns-1104.awsdns-10.org
  • ns-1893.awsdns-44.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

Threat-feed evidence

History

Related pages

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