Skip to content

Hostname

barebackbastards.com

Last fetched

barebackbastards.com resolves to 142.44.164.166, announced in 142.44.128.0/17 by OVH - OVH SAS in CA. barebackbastards.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 · barebackbastards.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/barebackbastards.com

Resolution chain

IPv6 resolution

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

Attribution

ovh

ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
pierre sorel
Contact emails
36b61d7bc221944b77ce1db011a757bc-953659@contact.gandi.net, e2f919496d8d3d40cdd5da4549e45f7a-953659@contact.gandi.net, ec59fa9c96e38f3e939ab3ed4ac7d683-953659@contact.gandi.net, edbf2fa81e7529c0bb0cf71876d1a277-953659@contact.gandi.net

Subdomains

Subdomain
video314.barebackbastards.com
video890.barebackbastards.com
www.barebackbastards.com

Showing 3 of 3 subdomains (3 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

  • ns-167-b.gandi.net
  • ns-215-c.gandi.net
  • ns-217-a.gandi.net
  • ns1.gandi.net
  • 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

  • mx00.ionos.de
  • mx01.ionos.de

SPF policy

  • include: _spf-eu.ionos.com

Threat-feed evidence

History

Related pages

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