Skip to content

Hostname

cury.net

Last fetched

cury.net resolves to 52.23.120.142, announced in 52.20.0.0/14 by AMAZON-AES - Amazon.com, Inc. in US. cury.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 · cury.netRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/cury.net

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:48
Registrant organisation
locaweb ltda.
Contact emails
regadmin@locaweb.com.br, registro.br@cury.net

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

  • ns1.locaweb.com.br
  • ns2.locaweb.com.br
  • ns3.locaweb.com.br
  • 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

  • cury-net.mail.protection.outlook.com

SPF policy

  • ip: 200.219.255.154/27
  • ip: 200.219.255.166/27
  • include: _spf.aremail.com.br
  • include: spf.sienge.com.br
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • mx: cury.net
  • ip: 168.245.50.141
  • ip: 179.191.124.43
  • ip: 200.170.251.234
  • ip: 52.54.170.158

Threat-feed evidence

History

Related pages

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