Skip to content

Hostname

mybind.com

Last fetched

mybind.com resolves to 3.211.123.4, announced in 3.208.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. mybind.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 · mybind.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/mybind.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
bolton, nick
Contact emails
nbolton.domains@gmail.com, 3ff76b1f-08f2-4613-b773-1d21f5ddf326@identity-protect.org, 4fd88035-57cd-4266-b6af-6844b5720390@identity-protect.org, 60268985-679a-4bf6-a3d0-4cb30a50ab10@identity-protect.org, 611a0a2a-0ef9-40e7-9e0b-0e2ae18866cd@identity-protect.org, 79cb7ed8-fc84-4a47-992b-ba30319accbb@identity-protect.org, ab1e4528-2ef3-4f67-89c4-4d86086bcb38@identity-protect.org, owner-4602338@mybind.com.whoisprivacyservice.org, owner-6918142@mybind.com.whoisprivacyservice.org, owner-7947150@mybind.com.whoisprivacyservice.org

Subdomains

Subdomain
daisy.mybind.com
dolly.mybind.com
mail.mybind.com
notifications.mybind.com
ns1.mybind.com
ns2.mybind.com
welcome.mybind.com
www.mybind.com

Showing 8 of 17. View all subdomains →

Mail and authentication

Nameservers

  • ns-121.awsdns-15.com
  • ns-745.awsdns-29.net
  • ns-1025.awsdns-00.org
  • ns-1814.awsdns-34.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

  • include: _spf.google.com
  • a: mybind.com
  • mx: mybind.com
  • include: _spf.qualtrics.com

Threat-feed evidence

History

Related pages

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