Skip to content

Hostname

nextly.net

Last fetched

nextly.net resolves to 155.133.132.3, announced in 155.133.128.0/20 by GANDI-AS-2 - GANDI SAS in FR. nextly.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 · nextly.netRouting diversity2.4/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.4/10canon.whisper.security/host/nextly.net

Resolution chain

IPv6 resolution

Attribution

gandi

ORIGIN_AS

WHOIS identity

Registrar
iana:68
Registrant organisation
barkan saeed
Contact emails
barkansaeed@gmail.com, 73558a694947457088a2bfc828317ea2.protect@whoisguard.com, 49ff8c050d1f8e7954130b27a82e68fd@proxy-service.fr, 02465c2dba206dd74a23faa33f350623-33829902@contact.gandi.net, 36ef0421bcfdfd4179c559beabb50601-48863215@contact.gandi.net, b9000c9c9c292d5dda525e130f537e5b-43588610@contact.gandi.net

Subdomains

Subdomain
ns1.nextly.net
panel.nextly.net
proxmox2.nextly.net

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns.hiwit.eu
  • ns.hiwit.fr
  • ns-100-a.gandi.net
  • ns-174-b.gandi.net
  • ns-246-c.gandi.net
  • ns1.he.net
  • ns2.he.net
  • ns3.he.net
  • ns4.he.net
  • ns5.he.net
  • ns.hiwit.net
  • ns105.hiwit.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

  • ns105.hiwit.net

Threat-feed evidence

History

Related pages

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