Skip to content

Hostname

batiksplus.com

Last fetched

batiksplus.com resolves to 162.255.119.51, announced in 162.255.119.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. batiksplus.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 · batiksplus.comRouting diversity2.4/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/batiksplus.com

Resolution chain

IPv6 resolution

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

Attribution

namecheap

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
batiksplus_com
Contact emails
contact@myprivateregistration.com, cookie@batiksplus.com, mudstuffing@gmail.com, 21663a20447241d0a7fcd13f9c43e0b6.protect@whoisguard.com, d81a55a456534156b79cfc6cad06e5a3.protect@whoisguard.com, 18b82e373bfd4c1aaf34b43f17fda1ee.protect@withheldforprivacy.com, e1775561d33b415b822f98836007ee4e.protect@withheldforprivacy.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

  • dns1.registrar-servers.com
  • dns2.registrar-servers.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

  • mx.spamexperts.com
  • win-mail17.hostmanagement.net

Threat-feed evidence

History

Related pages

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