Skip to content

Hostname

optimycdn.com

Last fetched

optimycdn.com resolves to 13.227.192.107, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. optimycdn.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 · optimycdn.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/optimycdn.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of optimycdn.com owner
Contact emails
12d79d4a-6fca-40ce-9b11-4afb009c5658@identity-protect.org, 444dedf0-8dd8-43e2-801f-032c7d59d038@identity-protect.org, 50d78c59-9b10-44ee-9eb5-c3e11ff7e7e0@identity-protect.org, 897ef07d-fd5b-4874-8475-d2b0a1243eb2@identity-protect.org, 90ac892b-9acc-41ed-918e-7a1dbbb07f2a@identity-protect.org, 90ef63d8-1381-4bde-a8e2-1ef617c8bfd0@identity-protect.org, f1a6a972-06bd-43c4-850e-f976f46bcd41@identity-protect.org

Subdomains

Mail and authentication

Nameservers

  • ns-86.awsdns-10.com
  • ns-952.awsdns-55.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-1043.awsdns-02.org
  • ns-2036.awsdns-62.co.uk

Threat-feed evidence

History

Related pages

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