Skip to content

Hostname

readysetsecure.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
axion health
Contact emails
girish@occhealthlink.com, 734ddd77-4102-4163-902d-b8eeeb988e14@identity-protect.org, 907130cc-41ed-4a39-b2a7-7fdc7f7e6aec@identity-protect.org, 927b39dc-b1ec-4336-aa97-b446f0a85509@identity-protect.org, c9bb76fa-655b-4b00-a7b4-8cd035e3a8be@identity-protect.org, f304ccb9-db73-40b6-ade7-0f8043caa76e@identity-protect.org, owner-2098935@readysetsecure.com.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-21.awsdns-02.com
  • ns-944.awsdns-54.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-1224.awsdns-25.org
  • ns-1634.awsdns-12.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: email-od.com
  • include: turbo-smtp.com
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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