Skip to content

Hostname

druganoga.com

Last fetched

druganoga.com resolves to 195.2.222.27, announced in 195.2.222.0/23 by LHPL - LH.pl Sp. z o.o. in PL. druganoga.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 · druganoga.comRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/druganoga.com

Resolution chain

IPv6 resolution

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

Attribution

lh pl sp

ORIGIN_AS

WHOIS identity

Registrar
iana:1456
Registrant organisation
whois data protection sp. z o.o.
Contact emails
bkjlajcdfaff-r@mail.netart-registrar.com, hshflelwpfxi-r@mail.netart-registrar.com, iblsqdqrluce-r@mail.netart-registrar.com, iqlwqpffhmwf-r@mail.netart-registrar.com, nrogvqkmfjou-r@mail.netart-registrar.com, gmcfxqnqmctb-r@mail.whoisdataprotection.com, rqklybrugqkb-r@mail.whoisdataprotection.com

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

  • 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
  • dns.home.pl
  • dns2.home.pl
  • dns3.home.pl

MX records

  • serwer2346078.home.pl

SPF policy

  • a: druganoga.com
  • mx: druganoga.com
  • include: _spf.mlsend.com
  • ip: 62.129.209.14

Threat-feed evidence

History

Related pages

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