Skip to content

Hostname

wellbin.co

Last fetched

wellbin.co resolves to 100.22.69.4, announced in 100.20.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. wellbin.co 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 · wellbin.coRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/wellbin.co

Resolution chain

IPv6 resolution

No AAAA record for wellbin.co is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
antena
Contact emails
79c3d81d27a8a0a91c0f0435d06dfde8-4557110@contact.gandi.net

Subdomains

Subdomain
cdn.wellbin.co
cdr.wellbin.co
config.wellbin.co
crm.wellbin.co
dashboards-crm.wellbin.co
demo.wellbin.co
encuestas.wellbin.co
fuego.wellbin.co
hidalgo.wellbin.co
kern-callcenter.wellbin.co
kern-derivaciones-stamboulian.wellbin.co
kern-derivaciones.wellbin.co

Showing 12 of 54. View all subdomains →

Mail and authentication

Nameservers

  • ns-2.awsdns-00.com
  • ns-524.awsdns-01.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-1501.awsdns-59.org
  • ns-1950.awsdns-51.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: amazonses.com
  • include: _spf.google.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

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