Skip to content

Hostname

hostmaster.netuseservers.com

Last fetched

hostmaster.netuseservers.com resolves to 217.151.107.11, announced in 217.151.107.0/24 by M247-UK - Convergence Group (Wireless) Networks Limited in GB. hostmaster.netuseservers.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 · hostmaster.netuseservers.comRouting diversity1.5/10Peering density5.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/hostmaster.netuseservers.com

Resolution chain

IPv6 resolution

No AAAA record for hostmaster.netuseservers.com is recorded in WhisperGraph.

Attribution

convergence group wireless

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for hostmaster.netuseservers.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Mail and authentication

Nameservers

  • ns1.netuseservers.com
  • ns2.netuseservers.com
  • ns3.netuseservers.com
  • ns4.netuseservers.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

  • mxa.netuse.co.uk

SPF policy

  • mx: hostmaster.netuseservers.com
  • ip: 217.151.107.11
  • ip: 217.151.107.12
  • ip: 217.151.107.13
  • ip: 217.151.107.14
  • ip: 217.151.107.15
  • ip: 217.151.107.16
  • ip: 217.151.107.17
  • ip: 217.151.107.18
  • ip: 217.151.107.4
  • ip: 89.238.157.36
  • ip: 89.238.165.34

Threat-feed evidence

History

Related pages

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