Hostname
considera.org
Last fetched
considera.org resolves to 104.21.45.38, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. considera.org is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.45.38
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.208.197
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.11
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.11
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:69
- Registrant organisation
- elemental solutions
- Contact emails
- mark.es@aecb.net
Subdomains
| Subdomain |
|---|
| cpanel.considera.org |
| cpcalendars.considera.org |
| cpcontacts.considera.org |
| macky.considera.org |
| mail.considera.org |
| webdisk.considera.org |
| webmail.considera.org |
| www.considera.org |
Showing 8 of 8 subdomains (8 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.
Mail and authentication
Nameservers
- ashley.ns.cloudflare.com
- jonah.ns.cloudflare.com
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
- mail.considera.org
SPF policy
- include: _spf.mailersend.net
- include: zcsend.net
- a: considera.org
- mx: considera.org
- include: relay.thundermail.uk
- ip: 149.255.58.124
- ip: 149.255.58.22
Threat-feed evidence
History
Related pages
Pivot from considera.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: "considera.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.