Skip to content

Hostname

overoption.io

Last fetched

overoption.io resolves to 108.156.201.15, announced in 108.156.200.0/22 by AMAZON-02 - Amazon.com, Inc. in US. overoption.io 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 · overoption.ioRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/overoption.io

Resolution chain

IPv6 resolution

No AAAA record for overoption.io is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
domains by proxy,

Subdomains

Subdomain
admin-affiliates.overoption.io
ads.overoption.io
affiliates.overoption.io
api-affiliates.overoption.io
api-tele.overoption.io
bugfixrf.overoption.io
dev-msc-affiliates.overoption.io
dev-notification.overoption.io
dev.overoption.io
devapi-tele.overoption.io
devapi.overoption.io
devbotapi.overoption.io

Showing 12 of 27. View all subdomains →

Mail and authentication

Nameservers

  • ns-372.awsdns-46.com
  • ns-561.awsdns-06.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-1349.awsdns-40.org
  • ns-1727.awsdns-23.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • a: overoption.io
  • mx: overoption.io
  • include: _04059cd91bf2c1a035470d0b1503c031.spf.dnssmarthost.net
  • ip: 34.175.13.143

Threat-feed evidence

History

Related pages

Pivot from overoption.io 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: "overoption.io"})-[: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.