Skip to content

Hostname

noovy.com

Last fetched

noovy.com resolves to 31.43.160.6, announced in 31.43.160.0/24 by AMAZON-02 - Amazon.com, Inc. in NL. noovy.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 · noovy.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/noovy.com

Resolution chain

IPv6 resolution

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

Attribution

amazon com

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of noovy.com owner
Contact emails
nocontactsfound@secureserver.net, 3ac686e0-fb06-4814-9ade-f8d1cbc995fa@identity-protect.org, 96d364f1-506b-4745-ad27-0d7132a4e9e4@identity-protect.org, b4799c15-4e72-4ade-bad4-e72087faa383@identity-protect.org, d31402db-cc29-4c32-8aa5-7357ce7cae5e@identity-protect.org, dfa94931-646b-4bcf-9534-b4e737facaa5@identity-protect.org, ed6dcd56-79c5-4a11-aace-5a3aae308877@identity-protect.org

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

  • ns-148.awsdns-18.com
  • ns-750.awsdns-29.net
  • ns-1057.awsdns-04.org
  • ns-1910.awsdns-46.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: hubspotemail.net
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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