Skip to content

Hostname

webaservers.net

Last fetched

webaservers.net resolves to 213.227.139.245, announced in 213.227.128.0/19 by LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. in NL. webaservers.net 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 · webaservers.netRouting diversity1.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/webaservers.net

Resolution chain

IPv6 resolution

No AAAA record for webaservers.net is recorded in WhisperGraph.

Attribution

leaseweb netherlands

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:82
Registrant organisation
domain id shield service
Contact emails
an1090701816602@domainidshield.com, webanchor.net@gmail.com, tayyab149@gmail.com

Subdomains

Subdomain
cpanel.webaservers.net
cpcalendars.webaservers.net
cpcontacts.webaservers.net
mail.webaservers.net
monitor.webaservers.net
ns1.webaservers.net
ns10.webaservers.net
ns11.webaservers.net
ns2.webaservers.net
ns5.webaservers.net
ns6.webaservers.net
resel.webaservers.net

Showing 12 of 20. View all subdomains →

Mail and authentication

Nameservers

  • ns5.webaservers.com
  • ns6.webaservers.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
  • ns5.webaservers.net
  • ns6.webaservers.net

MX records

  • webaservers.net

SPF policy

  • include: _spf.google.com
  • ip: 151.106.12.34
  • ip: 37.48.76.105
  • ip: 46.165.242.24

Threat-feed evidence

History

Related pages

Pivot from webaservers.net 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: "webaservers.net"})-[: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.