Skip to content

Hostname

connectingup.org

Last fetched

connectingup.org resolves to 54.153.222.148, announced in 54.153.128.0/17 by AMAZON-02 - Amazon.com, Inc. in AU. connectingup.org 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 · connectingup.orgRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/connectingup.org

Resolution chain

IPv6 resolution

No AAAA record for connectingup.org is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
cisa
Contact emails
cisaregister@cisa.asn.au, admin@connectingup.org

Subdomains

Subdomain
api.connectingup.org
click.connectingup.org
conference.connectingup.org
email.connectingup.org
help.connectingup.org
kb.connectingup.org
learning.connectingup.org
misc.connectingup.org
support.connectingup.org
track.connectingup.org
www.connectingup.org

Showing 11 of 11 subdomains (11 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • ns-206.awsdns-25.com
  • ns-827.awsdns-39.net
  • ns-1532.awsdns-63.org
  • ns-2012.awsdns-59.co.uk

MX records

  • connectingup-org.mail.protection.outlook.com

SPF policy

  • ip: 65.74.160.152/32
  • ip: 119.9.104.155/32
  • include: spf.autopilothq.com
  • include: _spf.createsend.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • include: sendgrid.net
  • mx: connectingup.org
  • include: mailgun.org

Threat-feed evidence

History

Related pages

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