Skip to content

Hostname

barneymillers.com

Last fetched

barneymillers.com resolves to 50.28.2.61, announced in 50.28.0.0/18 by LIQUIDWEB - Liquid Web, L.L.C in US. barneymillers.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 · barneymillers.comRouting diversity1.5/10Peering density5.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/barneymillers.com

Resolution chain

IPv6 resolution

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

Attribution

liquid

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
bz5zj8j54wk@networksolutionsprivateregistration.com, dx3649n2747@networksolutionsprivateregistration.com, vn29a3tb9q7@networksolutionsprivateregistration.com, vp8uc2te824@networksolutionsprivateregistration.com

Subdomains

Subdomain
email.barneymillers.com
intranet.barneymillers.com
membership.barneymillers.com
www.barneymillers.com

Showing 4 of 4 subdomains (4 per page).

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

  • ns85.worldnic.com
  • ns86.worldnic.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

  • barneymillers-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • ip: 50.28.2.61

Threat-feed evidence

History

Related pages

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