Skip to content

Hostname

nova53.net

Last fetched

nova53.net resolves to 193.30.34.47, announced in 193.30.34.0/24 by JURASSICINNOVATIONS - Jurassic Innovations, LLC in US. nova53.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 · nova53.netRouting diversity1.5/10Peering density3.1/10MOAS conflict⚠ 1 conflictThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/nova53.net

Resolution chain

IPv6 resolution

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

Attribution

jurassic innovations

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,

Subdomains

Subdomain
api.nova53.net
dcc.nova53.net
ddns.nova53.net
dev-ns2.nova53.net
dns.nova53.net
doh.nova53.net
fe-02.nova53.net
ideal.nova53.net
infra.nova53.net
jira.nova53.net
ns.nova53.net
proxy01-v4.nova53.net

Showing 12 of 25. View all subdomains →

Mail and authentication

Nameservers

  • perseus.ns.nova53.com
  • draco.ns.nova53.net
  • orion.ns.nova53.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
  • cygnus.ns.nova53.org

MX records

  • nova53-net.mx-a.mail.yinzcloud.net
  • nova53-net.mx-b.mail.yinzcloud.net
  • nova53-net.mx-c.mail.yinzcloud.net
  • nova53-net.mx-d.mail.yinzcloud.net

SPF policy

  • include: _spf.yinzcloud.net

Threat-feed evidence

History

Related pages

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