Skip to content

Hostname

citadelpathstatue.com

Last fetched

citadelpathstatue.com resolves to 172.240.41.123, announced in 172.240.41.0/24 by SERVERS-COM - Servers.com, Inc. in US. citadelpathstatue.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Tue, 15 Sep 2026 00:18:34 GMT

Nutrition Label

WHISPER CANON · citadelpathstatue.comRouting diversity1.5/10Peering density6.7/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/citadelpathstatue.com

Resolution chain

IPv6 resolution

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

Attribution

com

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
clickadu s.r.o.
Contact emails
support@clickadu.com, 5b023bf6-6c9e-4c9a-99b4-c349328243bd@identity-protect.org, df047806-e21b-452b-bb43-2faf2394c57b@identity-protect.org

Subdomains

Subdomain
www.citadelpathstatue.com

Showing 1 of 1 subdomain (1 per page).

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

Mail and authentication

Nameservers

  • ns-133.awsdns-16.com
  • ns-805.awsdns-36.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
  • ns-1341.awsdns-39.org
  • ns-1724.awsdns-23.co.uk

Threat-feed evidence

History

Related pages

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