Skip to content

Hostname

nuclear-power.com

Last fetched

nuclear-power.com resolves to 15.157.177.89, announced in 15.156.0.0/15 by AMAZON-02 - Amazon.com, Inc. in CA. nuclear-power.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 · nuclear-power.comRouting diversity2.4/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.9/10canon.whisper.security/host/nuclear-power.com

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:609
Registrant organisation
domain admin
Contact emails
admin@namedia.com, contact@privacyprotect.org

Subdomains

Subdomain
cdn-0.nuclear-power.com
cdn-1.nuclear-power.com
cdn-2.nuclear-power.com
cdn-3.nuclear-power.com
cdn-4.nuclear-power.com
cdn-5.nuclear-power.com
cdn-6.nuclear-power.com
cdn-7.nuclear-power.com
cdn.nuclear-power.com
mail.nuclear-power.com
radiation.nuclear-power.com
wildcard.nuclear-power.com

Showing 12 of 13. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • gecko.ezoicns.com
  • koala.ezoicns.com
  • macaw.ezoicns.com
  • quail.ezoicns.com
  • 1.ns.gigaserver.cz
  • 2.ns.gigaserver.cz
  • 3.ns.gigaserver.cz
  • 4.ns.gigaserver.cz
  • 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

  • mail.nuclear-power.com
  • mail.gigaserver.cz

Threat-feed evidence

History

Related pages

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