Skip to content

Hostname

crec.org

Last fetched

crec.org resolves to 20.230.16.73, announced in 20.192.0.0/10 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. crec.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 · crec.orgRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/crec.org

Resolution chain

IPv6 resolution

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

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
crec
Contact emails
dwu@crec.org, mkusiak@crec.org

Subdomains

Subdomain
2rivwindspire.crec.org
365mail.crec.org
antispam.crec.org
autodiscover.crec.org
chillrsswindsor.crec.org
coltweb.crec.org
cori.crec.org
crec-ev.crec.org
crecblog.crec.org
crecfiles.crec.org
crecmail.crec.org
crecroutes.crec.org

Showing 12 of 63. View all subdomains →

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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.cen.ct.gov
  • ns2.cen.ct.gov

MX records

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

SPF policy

  • ip: 143.55.232.0/24
  • ip: 50.223.178.203/32
  • ip: 64.28.179.72/32
  • include: spf.constantcontact.com
  • include: _spf.psm.knowbe4.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • include: customerspf.schoolmessenger.com
  • include: mail.zendesk.com
  • ip: 13.68.113.27
  • ip: 143.55.227.190
  • ip: 72.10.104.150
  • ip: 72.10.104.161
  • ip: 72.10.104.206

Threat-feed evidence

History

Related pages

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