Skip to content

Hostname

mywiseboard.com

Last fetched

mywiseboard.com resolves to 51.77.119.185, announced in 51.77.0.0/16 by OVH - OVH SAS in GB. mywiseboard.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 · mywiseboard.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/mywiseboard.com

Resolution chain

IPv6 resolution

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

Attribution

ovh

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of mywiseboard.com owner
Contact emails
2e1e746b-40b8-45a7-8e1c-016790d869a6@identity-protect.org, 45685755-5b24-40af-bbe5-b711db6aeb70@identity-protect.org, aa3ec4f0-de10-4ba6-b306-df65bdfb7579@identity-protect.org, ae939f6b-1172-4b44-ab11-b2c31c78995b@identity-protect.org, f401e2c0-8f2e-48df-89c0-1bdd4b360145@identity-protect.org, f8438c3c-368a-4187-acf9-81271724e11d@identity-protect.org, owner-3564188@mywiseboard.com.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-159.awsdns-19.com
  • ns-824.awsdns-39.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-1094.awsdns-08.org
  • ns-2032.awsdns-62.co.uk

MX records

  • mail.mywiseboard.com

SPF policy

  • a: mywiseboard.com
  • mx: mywiseboard.com
  • a: ns3145533.ip-51-77-119.eu

Threat-feed evidence

History

Related pages

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