Skip to content

Hostname

computerrehab.us

Last fetched

computerrehab.us resolves to 161.97.219.84, announced in 161.97.192.0/18 by COL-LPC - Longmont Power & Communications in US. computerrehab.us 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 · computerrehab.usRouting diversity2.4/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/computerrehab.us

Resolution chain

IPv6 resolution

Attribution

longmont power

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
computer rehab
Contact emails
shdwdrgn@sourpuss.net

Subdomains

Subdomain
cp.computerrehab.us
mail.computerrehab.us
mx1.computerrehab.us
mx2.computerrehab.us
ns1.computerrehab.us
ns2.computerrehab.us
ns5.computerrehab.us
smtp.computerrehab.us
www.computerrehab.us

Showing 9 of 9 subdomains (9 per page).

Mail and authentication

Nameservers

  • 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
  • ns1.sourpuss.net
  • ns2.sourpuss.net
  • ns5.sourpuss.net
  • ns1.computerrehab.us
  • ns2.computerrehab.us
  • ns5.computerrehab.us

MX records

  • mx5.sourpuss.net
  • mx1.computerrehab.us
  • mx2.computerrehab.us

SPF policy

  • ip: 2001:470:4212::/48
  • ip: 2602:3f:e75c:1b00::/59
  • ip: 161.97.219.80/29
  • a: mx1.sourpuss.net
  • a: mx2.sourpuss.net
  • a: mx5.sourpuss.net
  • a: smtp.sourpuss.net
  • a: computerrehab.us
  • a: mx1.computerrehab.us
  • a: mx2.computerrehab.us
  • ip: 63.231.92.27

Threat-feed evidence

History

Related pages

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