Skip to content

Hostname

devotableapp.com

Last fetched

devotableapp.com resolves to 172.234.24.211, announced in 172.234.16.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. devotableapp.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 · devotableapp.comRouting diversity2.4/10Peering density6.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/devotableapp.com

Resolution chain

IPv6 resolution

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
2b5a094758e94cf59bc7831096927c69.protect@whoisguard.com, 5f8bcf3450e34247a55d88dda166e56d.protect@withheldforprivacy.com, reactivation-pending@mail.withheldforprivacy.com

Subdomains

Subdomain
test.devotableapp.com
www.devotableapp.com

Showing 2 of 2 subdomains (2 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

Sample outbound links

Mail and authentication

Nameservers

  • luciane.ns.cloudflare.com
  • roman.ns.cloudflare.com
  • dns1.registrar-servers.com
  • dns101.registrar-servers.com
  • dns102.registrar-servers.com
  • dns2.registrar-servers.com
  • 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

  • mx.plingest.com

Threat-feed evidence

History

Related pages

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